Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1518334

Summary: [UPDATES] resource_registry is not updated correctly
Product: Red Hat OpenStack Reporter: Yurii Prokulevych <yprokule>
Component: openstack-tripleo-commonAssignee: Lukas Bezdicka <lbezdick>
Status: CLOSED ERRATA QA Contact: Yurii Prokulevych <yprokule>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: aschultz, augol, jschluet, mbracho, mbultel, mburns, sclewis, slinaber, tvignaud
Target Milestone: gaKeywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-tripleo-common-7.6.3-8.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 22:23:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Yurii Prokulevych 2017-11-28 16:15:15 UTC
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):

How reproducible:

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

Comment 1 Amit Ugol 2017-11-29 09:12:00 UTC
The issue in this case is that puppet should not run at all during this stage, only when you run 'stack update --nodes ...'

Comment 2 Lukas Bezdicka 2017-11-29 15:19:04 UTC
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.

Comment 8 Yurii Prokulevych 2017-12-12 14:34:12 UTC
Verified with openstack-tripleo-common-7.6.3-8.el7ost.noarch

Comment 11 errata-xmlrpc 2017-12-13 22:23:28 UTC
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.