Bug 1457208

Summary: tripleo client stuck in IN_PROGRESS in overcloud update run
Product: Red Hat OpenStack Reporter: Martin Schuppert <mschuppe>
Component: openstack-tripleo-commonAssignee: Julie Pichon <jpichon>
Status: CLOSED ERRATA QA Contact: Yurii Prokulevych <yprokule>
Severity: urgent Docs Contact:
Priority: high    
Version: 9.0 (Mitaka)CC: apannu, aschultz, cpaquin, dbecker, hbrock, hjensas, jjoyce, jpichon, jslagle, mburns, mschuppe, pneedle, rhel-osp-director-maint, sgordon, slinaber, therve, yprokule
Target Milestone: zstreamKeywords: OtherQA, Triaged, ZStream
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-common-2.0.0-11.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1437016
: 1520109 (view as bug list) Environment:
Last Closed: 2017-07-12 13:02:04 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: 1437016    
Bug Blocks: 1434509, 1520109    

Comment 1 Red Hat Bugzilla Rules Engine 2017-05-31 10:48:47 UTC 
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Comment 3 Julie Pichon 2017-06-01 14:54:10 UTC 
I am trying to reproduce the issue in an OSP9 environment, following the steps from the original bug (make an stack update fail, fix up the plan, run another stack update). Unfortunately I can't reproduce the hanging issue so far; the second update completes successfully.
Comment 20 Yurii Prokulevych 2017-07-11 10:15:58 UTC 
Verified with openstack-tripleo-common-2.0.0-11.el7ost.noarch
Successfully re-run update after failed attempt.
Comment 23 errata-xmlrpc 2017-07-12 13:02:04 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-2017:1734