Bug 1399769

Summary: No error message displayed by the WebUi if the connection to the appliance is lost while on certain forms, such as the migration request
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: UI - OPSAssignee: lgalis
Status: CLOSED ERRATA QA Contact: Leo Khomenko <lkhomenk>
Severity: high Docs Contact:
Priority: high    
Version: 5.6.0CC: cpelland, dajohnso, hkataria, jfrey, jhardy, lkhomenk, mpovolny, obarenbo, ronny.pfannschmidt, simaishi
Target Milestone: GAKeywords: ZStream
Target Release: 5.6.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.6.4.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1378481 Environment:
Last Closed: 2017-03-09 17:04:44 UTC Type: ---
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: 1378481    
Bug Blocks:    

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