In general, existence swift container "overcloud" is not a issue for deployment. Bug is fixed https://bugs.launchpad.net/tripleo/+bug/1622683 By some reasons it appears to be an issue on QuickStart ( might be due to different design) ________________________________ From: rdo-list-bounces(a)redhat.com <rdo-list-bounces(a)redhat.com&gt; on behalf of Boris Derzhavets <bderzhavets(a)hotmail.com&gt; Sent: Saturday, October 15, 2016 10:29 AM To: rdo-list; John Trowbridge Subject: [rdo-list] Failure to deploy overcloud via TripleO StartQuickStart In meantime indercloud gets created with swift container "overcloud" already been built. It results failure to start Mistral Work-flow by script :- #!/bin/bash -x source /home/stack/stackrc openstack overcloud deploy \ --control-scale 3 --compute-scale 1 \ --libvirt-type qemu \ --ntp-server pool.ntp.org \ --templates /usr/share/openstack-tripleo-heat-templates \ -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml \ -e $HOME/network_env.yaml Attempt `swift delete overcloud` and restart deployment fails to start Mistral work-flow either way. Changes seems to be done a bit latter 10/13/16 (GMT+4) due to 10/12-10/13 old schema still worked experiencing some delay during updating plan and starting mistral work flow. However, command `bash quickstart.sh -R newton --config ./config/general_config/ha.yml $VIRTHOST` still completes with old instructions ################################## Virtual Environment Setup Complete ################################## Access the undercloud by: ssh -F /home/jon/.quickstart/ssh.config.ansible undercloud Follow the documentation in the link below to complete your deployment. http://ow.ly/c44w304begR <== standard instructions from tripleo.org which seems to be outdated at the moment . I cannot proceed with script above when swift container "overcloud" already exists. Thanks. Boris.

Newton trunk "centos7-newton/current-passed-ci" got renewed. Instack-virt-setup works with Network isolation with no problems again. Just nodes are introspected sequentially ( no bulk). I am wondering is there any trigger which initiate building new Newton trunk "centos7-newton/current-passed-ci". Just see new content in http://buildlogs.centos.org/centos/7/cloud/x86_64/rdo-trunk-newton-tested... and understand that trunk "current-passed-ci" has been rebuilt. One more notice I set up KSM and KSMTUNED ( only services started and enabled with default values ) on VIRTHOST running instack-virt-setup. Performance improvement and memory allocation look pretty close to TripleO QuickStart. So far I don't negative drawback from daemon ksmd up and running on VIRTHOST. [cid:d5ccc703-da58-42d2-b7e3-2b001010a8ac] Thanks. Boris ________________________________ From: rdo-list-bounces(a)redhat.com <rdo-list-bounces(a)redhat.com&gt; on behalf of Boris Derzhavets <bderzhavets(a)hotmail.com&gt; Sent: Sunday, October 16, 2016 11:54 AM To: rdo-list Subject: [rdo-list] The most recent Newton trunk "centos7-newton/current-passed-ci" and instack-virt-setup issue Set up repos on VIRTHOST and INSTACK VM sudo yum -y install yum-plugin-priorities sudo curl -o /etc/yum.repos.d/delorean-newton.repo \ http://buildlogs.centos.org/centos/7/cloud/x86_64/rdo-trunk-newton-tested... sudo curl -o /etc/yum.repos.d/delorean-deps-newton.repo \ https://trunk.rdoproject.org/centos7-newton/delorean-deps.repo Register 4 nodes $ openstack baremetal import instackenv.json OK $ openstack baremetal configure boot OK $ openstack baremetal introspection bulk start HANGS Attempt to introspecting a Single Node<http://tripleo.org/advanced_deployment/introspect_single_node.htm... for each entry entry in `ironic node-list` finally get introspection status "Finished - True" and move to available via 'ironic node-set-provision-state UUID provide` Procedure works for deployment #!/bin/bash -x source /home/stack/stackrc openstack overcloud deploy \ --control-scale 3 --compute-scale 1 \ --libvirt-type qemu \ --ntp-server pool.ntp.org \ --templates /usr/share/openstack-tripleo-heat-templates Then drop all VMs and start from scratch same procedure Attempt to deploy :- Interface vlan10 added && network_env.yaml created in ~stack/ folder #!/bin/bash -x source /home/stack/stackrc openstack overcloud deploy \ --control-scale 3 --compute-scale 1 \ --libvirt-type qemu \ --ntp-server pool.ntp.org \ --templates /usr/share/openstack-tripleo-heat-templates \ -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml \ -e $HOME/network_env.yaml Only 2 VMst boot the other 2 VMs fail to boot . Console reports IPXE failure . Heat session reports "not enough nodes available" error 500 . Deployment fails. Previous Newton trunk "current-passed-ci" ( around 10/11/16 ) worked fine. $ openstack baremetal introspection bulk start Completed OK , no further issues. Redeployment still works fine after reboot to another CentOS 7.2 instance . ( several CentOS 7.2 instances multibooting ) Thanks. Boris.