Hide Forgot
Description of problem: Existing nodes get rebuild on a 2nd overcloud deploy run, after the overcloud-full image has been updated. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Deploy overcloud: source ~/stackrc export THT=/usr/share/openstack-tripleo-heat-templates openstack overcloud deploy --templates \ -e $THT/environments/network-isolation.yaml \ -e $THT/environments/network-management.yaml \ -e ~/templates/network-environment.yaml \ -e ~/templates/enable-tls.yaml \ -e ~/templates/inject-trust-anchor.yaml \ -e ~/templates/tls-endpoints-public-ip.yaml \ -e ~/templates/password-env.yaml \ --control-scale 1 \ --control-flavor controller-d75f3dec-c770-5f88-9d4c-3fea1bf9c484 \ --compute-scale 1 \ --compute-flavor compute-b634c10a-570f-59ba-bdbf-0c313d745a10 \ --ntp-server clock.redhat.com 2. Update image: [stack@undercloud-0 ~]$ openstack overcloud image upload --update-existing Image "overcloud-full-vmlinuz" is up-to-date, skipping. Image "overcloud-full-initrd" is up-to-date, skipping. Image "overcloud-full" was uploaded. +--------------------------------------+----------------+-------------+------------+--------+ | ID | Name | Disk Format | Size | Status | +--------------------------------------+----------------+-------------+------------+--------+ | bce2b65d-ebbf-4e62-a5fd-b5891539b980 | overcloud-full | qcow2 | 1208811520 | active | +--------------------------------------+----------------+-------------+------------+--------+ Image "bm-deploy-kernel" is up-to-date, skipping. Image "bm-deploy-ramdisk" is up-to-date, skipping. Image file "/httpboot/agent.kernel" is up-to-date, skipping. Image file "/httpboot/agent.ramdisk" is up-to-date, skipping. 3. Rerun deploy command: source ~/stackrc export THT=/usr/share/openstack-tripleo-heat-templates openstack overcloud deploy --templates \ -e $THT/environments/network-isolation.yaml \ -e $THT/environments/network-management.yaml \ -e ~/templates/network-environment.yaml \ -e ~/templates/enable-tls.yaml \ -e ~/templates/inject-trust-anchor.yaml \ -e ~/templates/tls-endpoints-public-ip.yaml \ -e ~/templates/password-env.yaml \ --control-scale 1 \ --control-flavor controller-d75f3dec-c770-5f88-9d4c-3fea1bf9c484 \ --compute-scale 1 \ --compute-flavor compute-b634c10a-570f-59ba-bdbf-0c313d745a10 \ --ntp-server clock.redhat.com Actual results: [stack@undercloud-0 ~]$ nova list +--------------------------------------+-------------------------+---------+------------------+-------------+-----------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+-------------------------+---------+------------------+-------------+-----------------------+ | da06c2f6-b2c9-4213-a571-5034d7cdd97c | overcloud-controller-0 | REBUILD | rebuild_spawning | Running | ctlplane=192.168.0.21 | | 9e99df07-93c8-4666-842b-b9f9c722710b | overcloud-novacompute-0 | REBUILD | rebuild_spawning | Running | ctlplane=192.168.0.13 | +--------------------------------------+-------------------------+---------+------------------+-------------+-----------------------+ Expected results: Existing nodes don't get rebuilt.
Version-Release number of selected component (if applicable): python-tripleoclient-5.0.0-0.20160907170033.b0d7ce7.el7ost.noarch openstack-tripleo-heat-templates-5.0.0-0.20160907212643.90c852e.1.el7ost.noarch openstack-heat-common-7.0.0-0.20160907124808.21e49dc.el7ost.noarch python-heatclient-1.4.0-0.20160831084943.fb7802e.el7ost.noarch openstack-heat-templates-0.0.1-0.20160906185549.ac2db55.el7ost.noarch openstack-heat-api-cfn-7.0.0-0.20160907124808.21e49dc.el7ost.noarch openstack-heat-engine-7.0.0-0.20160907124808.21e49dc.el7ost.noarch puppet-heat-9.2.0-0.20160901072004.4d7b5be.el7ost.noarch openstack-heat-api-7.0.0-0.20160907124808.21e49dc.el7ost.noarch python-heat-tests-7.0.0-0.20160907124808.21e49dc.el7ost.noarch How reproducible: 100%
jistr, can you have a look at this one?
Yup
We had this problem in OSP 9 (bug 1354627) and it was fixed by Thomas, but the fix fell under the radar upstream so it's missing in OSP 10. It's now targeted for Newton RC2.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-2948.html