Bug 1546122
| Summary: | UI does not notify on failed plan update | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Julie Pichon <jpichon> |
| Component: | openstack-tripleo-ui | Assignee: | Jiri Tomasek <jtomasek> |
| Status: | CLOSED ERRATA | QA Contact: | Udi Kalifon <ukalifon> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 13.0 (Queens) | CC: | apannu, augol, jjoyce, jrist, jschluet, jtomasek, slinaber, tvignaud |
| Target Milestone: | Upstream M3 | Keywords: | Triaged |
| Target Release: | 14.0 (Rocky) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-ui-9.3.1-0.20180921180341.df30b55.el7ost.noarch.rpm | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-01-11 11:48:46 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: | 1560579 | ||
| Bug Blocks: | |||
|
Description
Julie Pichon
2018-02-16 11:50:04 UTC
Appears to occur with both Firefox and Chrome. After some team effort debugging, we discovered that the original tarballs used in this bug were faulty and that was the reason the plan update didn't work. When attempting a plan update with a correct tarball, it works fine. However, the issue of UI not displaying a failure message on failed plan update is still relevant. So this bug should be about fixing the UI so that it properly displays a failure message when a plan update fails. After some more investigation, this is down to the Swift API not returning the correct status code. See bz 1560579 for more detail. I wasn't able to make it fail. Verified: openstack-tripleo-ui-9.3.1-0.20180921180341.df30b55.el7ost.noarch 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/RHEA-2019:0045 |