Bug 1462377 - Reload Current Display button does not work when promoting a role to primary in diagnostics
Summary: Reload Current Display button does not work when promoting a role to primary ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: GA
: cfme-future
Assignee: Dan Clarizio
QA Contact: Raoul Snyman
URL:
Whiteboard: diagnostic:worker
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-16 23:19 UTC by Jeffrey Cutter
Modified: 2019-08-06 20:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:
dajohnso: automate_bug?


Attachments (Terms of Use)

Description Jeffrey Cutter 2017-06-16 23:19:06 UTC
Description of problem:

If in a multi appliance region you go to appliance configuration, diagnostics, roles by server and promote a role to primary when the role was not already running there, the status does not update immediately and the Reload Current Display button does not work.  You can verify this using a separate browser window to verify the state has changed while the refresh button is unable to detect it.  Clicking elsewhere and clicking back refreshes.

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

5.7.2.1.20170406142927_0a1ad0e

How reproducible:

Always

Comment 2 Dave Johnson 2017-06-23 21:41:12 UTC
Jeff, can you assess the customer impact on this one and update the severity field accordingly.  Thanks!

Please review https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for their definitions.

Comment 3 Raoul Snyman 2018-08-02 18:53:21 UTC
I just tried this on a 5.8.4.5.20180618175258_5bee58a setup, and I cannot reproduce the bug. It appears to work correctly.

Comment 4 Josh Carter 2018-10-02 14:33:14 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 5 Josh Carter 2018-10-02 14:33:57 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 6 Josh Carter 2018-10-02 14:35:25 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!


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