Red Hat Bugzilla – Bug 1518334
[UPDATES] resource_registry is not updated correctly
Last modified: 2018-02-05 14:18:02 EST
Description of problem: ----------------------- Puppet is running on overcloud nodes during init minor update. openstack overcloud update stack --init-minor-update \ --container-registry-file docker.yaml Version-Release number of selected component (if applicable): ------------------------------------------------------------- openstack-tripleo-puppet-elements-7.0.1-1.el7ost.noarch openstack-tripleo-common-containers-7.6.3-4.el7ost.noarch python-tripleoclient-7.3.3-5.el7ost.noarch puppet-tripleo-7.4.3-9.el7ost.noarch openstack-tripleo-common-7.6.3-4.el7ost.noarch openstack-tripleo-ui-7.4.3-4.el7ost.noarch openstack-tripleo-validations-7.4.2-1.el7ost.noarch openstack-tripleo-heat-templates-7.0.3-13.el7ost.noarch openstack-tripleo-image-elements-7.0.1-1.el7ost.noarch How reproducible: ----------------- 100% Steps to Reproduce: 1. Setup repos on oc nodes 2. Get latest docker images 3. Run: openstack overcloud update stack --init-minor-update \ --container-registry-file docker.yaml
The issue in this case is that puppet should not run at all during this stage, only when you run 'stack update --nodes ...'
The 'OS::TripleO::DeploymentSteps': 'OS::Heat::None' does not get set to none during init-minor-update and it runs Deployment_StepX tasks which means running puppet on nodes during the run. This is regression from previous state where init-minor-update just creates heat outputs.
Verified with openstack-tripleo-common-7.6.3-8.el7ost.noarch
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://access.redhat.com/errata/RHEA-2017:3462