Bug 1399769 - No error message displayed by the WebUi if the connection to the appliance is lost while on certain forms, such as the migration request
Summary: No error message displayed by the WebUi if the connection to the appliance is...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.4
Assignee: lgalis
QA Contact: Leo Khomenko
URL:
Whiteboard:
Depends On: 1378481
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-29 17:02 UTC by Satoe Imaishi
Modified: 2017-03-09 17:04 UTC (History)
10 users (show)

Fixed In Version: 5.6.4.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1378481
Environment:
Last Closed: 2017-03-09 17:04:44 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0474 0 normal SHIPPED_LIVE CFME 5.6.4 bug fixes and enhancement update 2017-03-09 22:03:14 UTC

Comment 2 lgalis 2016-12-01 14:16:17 UTC 
https://github.com/ManageIQ/manageiq/pull/12785
Comment 3 lgalis 2017-01-30 18:35:50 UTC 
https://github.com/ManageIQ/manageiq/pull/13690
Comment 5 lgalis 2017-02-09 15:19:34 UTC 
Failing to connect to CF is not a regular failure, it is catastrophic failure. 
There will be no different error shown nor will the error go away.
If we switch to only have one of these type of alerts displayed, it will seem like nothing really happens on the screen.
So, in this case, for this type of failure, I think multiple messages as shown here are necessary.
Comment 6 Leo Khomenko 2017-02-09 15:39:29 UTC 
ok. if that is by design - we may mark this as Verified
Comment 8 errata-xmlrpc 2017-03-09 17:04:44 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://rhn.redhat.com/errata/RHBA-2017-0474.html
Note You need to log in before you can comment on or make changes to this bug.