Bug 1457208 - tripleo client stuck in IN_PROGRESS in overcloud update run
Summary: tripleo client stuck in IN_PROGRESS in overcloud update run
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: zstream
: 9.0 (Mitaka)
Assignee: Julie Pichon
QA Contact: Yurii Prokulevych
URL:
Whiteboard:
Depends On: 1437016
Blocks: 1434509 1520109
TreeView+ depends on / blocked
 
Reported: 2017-05-31 10:48 UTC by Martin Schuppert
Modified: 2021-03-11 15:16 UTC (History)
17 users (show)

Fixed In Version: openstack-tripleo-common-2.0.0-11.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1437016
: 1520109 (view as bug list)
Environment:
Last Closed: 2017-07-12 13:02:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1677548 0 None None None 2017-05-31 10:48:27 UTC
OpenStack gerrit 452626 0 'None' 'MERGED' 'Handle re-created resources in StackUpdateManager' 2019-11-28 11:22:54 UTC
Red Hat Knowledge Base (Solution) 3113281 0 None None None 2017-07-13 08:39:06 UTC
Red Hat Product Errata RHBA-2017:1734 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 9 director Bug Fix Advisory 2017-07-12 17:01:34 UTC

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
Note You need to log in before you can comment on or make changes to this bug.