Bug 1306823 - Revise table behavior on RHEV engine selection
Summary: Revise table behavior on RHEV engine selection
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: WebUI
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.1
Assignee: Derek Whatley
QA Contact: Tasos Papaioannou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-11 19:35 UTC by Matt Reid
Modified: 2017-02-28 01:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-28 01:37:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:0335 0 normal SHIPPED_LIVE Red Hat Quickstart Installer 1.1 2017-02-28 06:36:13 UTC

Description Matt Reid 2016-02-11 19:35:22 UTC
Description of problem:
Some users got hung up trying to swap selected engine/hypervisor systems. Right now if you select a hypervisor, and go back to engine selection, the system you picked to be a hypervisor doesn't show in the table (since it's already selected on the next step). The workaround that people came up with was to start over. 

We should look into altering the table behavior here, potentially to show the hypervisor systems in the engine table as unselectable, with a tooltip saying they're going to be a hypervisor. 

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


Additional info:

Comment 1 Derek Whatley 2016-09-19 14:27:14 UTC
https://github.com/fusor/fusor/pull/1228

Comment 2 Derek Whatley 2016-09-20 21:55:21 UTC
Additional PR duplicating changes to the RHV Engine selection table:
https://github.com/fusor/fusor/pull/1230

Comment 3 Tasos Papaioannou 2016-10-05 20:02:02 UTC
Verified on QCI-1.1-RHEL-7-20161004.t.0.

Comment 6 errata-xmlrpc 2017-02-28 01:37:51 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://access.redhat.com/errata/RHEA-2017:0335


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