Bug 1477730

Summary: split-stack minor update does not prompt to clear breakpoints
Product: Red Hat OpenStack Reporter: James Slagle <jslagle>
Component: openstack-tripleo-commonAssignee: Toure Dunnon <tdunnon>
Status: CLOSED ERRATA QA Contact: Gurenko Alex <agurenko>
Severity: high Docs Contact:
Priority: high    
Version: 11.0 (Ocata)CC: agurenko, aschultz, augol, dbecker, emacchi, mburns, mlopes, morazi, ohochman, rhel-osp-director-maint, slinaber
Target Milestone: z4Keywords: Triaged, ZStream
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-common-6.1.2-1.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1477729 Environment:
Last Closed: 2018-02-13 16:31:14 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:
Embargoed:
Bug Depends On: 1477729    
Bug Blocks:    

Description James Slagle 2017-08-02 18:18:11 UTC
+++ This bug was initially created as a clone of Bug #1477729 +++

When doing a minor update:

openstack overcloud update stack -i overcloud

with split-stack using pre-provisioned nodes, you are never prompted to clear any breakpoints. The client finishes running but the Heat stack is still stuck in progress until breakpoints are cleared.

This is due to the code in tripleo-common querying nova for server names and id's, but there are no nova servers when using pre-provisioned nodes. In that case, we will have to query Heat directly for the names and id's.

Comment 4 Gurenko Alex 2017-12-07 09:39:25 UTC
Verified with minor update from 2017-12-04.1 to 2017-12-05.1

Comment 7 errata-xmlrpc 2018-02-13 16:31:14 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.

https://access.redhat.com/errata/RHBA-2018:0310