resource_registry is not updated correctly during minor update causing puppet to run

Bug #1735330 reported by Alex Schultz on 2017-11-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Thomas Herve

Bug Description

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

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.

Alex Schultz (alex-schultz) wrote :
Changed in tripleo:
status: Triaged → Fix Released
assignee: nobody → Thomas Herve (therve)

Submitter: Zuul
Branch: stable/pike

commit cbaf576f1a988a059e69ff6aa7ab094cedfa8abe
Author: Thomas Herve <email address hidden>
Date: Wed Nov 29 10:22:53 2017 +0100

    Consume resource-registry in ProcessTemplatesAction

    Retrieve the registry from the plan and pass it to stack operation later

    Closes-Bug: #1735330
    Change-Id: I1bb33796afa2c6d9a2bd7202e05075924f93da5d
    (cherry picked from commit 29f875e1f618274b6baf6cdee474c98ea0bc4fdc)

tags: added: in-stable-pike

This issue was fixed in the openstack/tripleo-common 7.6.6 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers