Bug 1310910 - CFME UI becomes inaccessible after entering bad credentials for RHEV host
CFME UI becomes inaccessible after entering bad credentials for RHEV host
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance (Show other bugs)
Unspecified Unspecified
high Severity high
: GA
: 5.6.0
Assigned To: Boriso
Nandini Chandra
Depends On:
  Show dependency treegraph
Reported: 2016-02-22 18:51 EST by Nandini Chandra
Modified: 2016-06-29 04:02 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-05-31 03:36:22 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nandini Chandra 2016-02-22 18:51:04 EST
Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Manage a RHEV provider(Tested RHEV 3.4)
2.Add default credentials to the RHEV host.Click 'Configuration', click 'Edit this item'.
3.Enter credentials in the Default tab and hit the 'Validate' button.

Actual results:
UI becomes inaccessible

Expected results:
UI should remain accessible.

Additional info:
This issue is only seen in 5.4 and not 5.5.
Comment 2 Joe Rafaniello 2016-03-08 12:06:56 EST
Hi Greg, 

Do you think this is related to the code that checks if the authentication is valid before starting the worker?  If so, I don't know how easy that is to backport to 5.4. I don't know that this would cause the UI to become unresponsive but if the worker continually restarts, I suppose the system could become unstable.  Can you have someone investigate and let me know if I can help?

Comment 4 Oved Ourfali 2016-05-10 01:42:45 EDT
Nandini, we don't see the issue in 5.6.
Can you check if it reproduces for you?
Comment 5 Nandini Chandra 2016-06-29 04:02:25 EDT

This issue can't be reproduced in 5.6.

Note You need to log in before you can comment on or make changes to this bug.