Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
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
No error message displayed by the WebUi if the connection to the appliance is...
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS (Show other bugs)
5.6.0
Unspecified Unspecified
high Severity high
: GA
: 5.6.4
Assigned To: lgalis
Leo Khomenko
: ZStream
Depends On: 1378481
Blocks:
  Show dependency treegraph
 
Reported: 2016-11-29 12:02 EST by Satoe Imaishi
Modified: 2017-03-09 12:04 EST (History)
10 users (show)

See Also:
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 12:04:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0474 normal SHIPPED_LIVE CFME 5.6.4 bug fixes and enhancement update 2017-03-09 17:03:14 EST

  None (edit)
Comment 5 lgalis 2017-02-09 10:19:34 EST
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 10:39:29 EST
ok. if that is by design - we may mark this as Verified
Comment 8 errata-xmlrpc 2017-03-09 12:04:44 EST
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.