Bug 1397852
| Summary: | python-tripleoclient should print the event list and not exit until the stack is in a COMPLETE or FAILED state | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> |
| Component: | python-tripleoclient | Assignee: | Brad P. Crochet <brad> |
| Status: | CLOSED ERRATA | QA Contact: | Gurenko Alex <agurenko> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 10.0 (Newton) | CC: | apevec, aschultz, brad, dbecker, dhill, fahmed, fdinitto, hbrock, jcoufal, jschluet, jslagle, lhh, mburns, mcornea, morazi, ohochman, rhel-osp-director-maint, samccann, sbaker, sclewis, srevivo, whayutin |
| Target Milestone: | z5 | Keywords: | TestOnly, Triaged, ZStream |
| Target Release: | 10.0 (Newton) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-tripleoclient-5.4.2-1.el7ost openstack-tripleo-common-5.4.2-2.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
The CLI would not block when stack update is performed. As such, a user could inadvertently think that the update was complete when it was not, and try again, not realizing that state of the stack was still in progress.
This fix will now block the CLI until the stack update is complete.
|
Story Points: | --- |
| Clone Of: | 1384246 | Environment: | |
| Last Closed: | 2017-09-28 16:35:22 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: | 1384246 | ||
| Bug Blocks: | 1384288, 1389195, 1389196 | ||
|
Comment 7
Lon Hohberger
2017-09-06 19:56:53 UTC
According to our records, this should be resolved by openstack-tripleo-common-5.4.2-3.el7ost. This build is available now. Verified on build 2017-09.20.2. Scaling back up worked as expected after removal of compute node. 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:2825 |