Bug 1400373 - RHV hypervisor+engine deployment- Allow reselecting nodes at 2B after proceeding to 2C and then going back to 2B
Summary: RHV hypervisor+engine deployment- Allow reselecting nodes at 2B after proceed...
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: cchase
QA Contact: James Olin Oden
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-01 02:29 UTC by Julie
Modified: 2017-02-28 01:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-28 01:41:44 UTC
Target Upstream Version:


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 Julie 2016-12-01 02:29:55 UTC
Version-Release number of selected component (if applicable):
QCI 1.1 Nov28 ISO

Steps to Reproduce:
1. Deploy RHV (engine + hypervisor)
2. Get to 2B and select the node prepared for the hypervisor instead of the engine node. Click Next.
3. At 2C realize the mistake and want to change the selection in 2B.

Actual results:
Cannot change the selected nodes.

Expected results:
Can change selected nodes at 2B after proceeding to 2C and then coming back to 2B. 

Workaround: Go to 2A and change to self-hosted, click next, and then go back to 2A and change back to engine + hypervisor. The nodes will be available to select again.

Comment 2 Jason Montleon 2016-12-05 20:53:23 UTC
I just checked this in the latest 1.1 ISO and as long as I haven't selected a discovered host to be a hypervisor I can go back to 2B and choose it as the engine without a problem.

Comment 3 Julie 2016-12-05 23:52:48 UTC
(In reply to Jason Montleon from comment #2)
yeah, I think I did click the remaining discovered host to be hypervisor and then can't go back and change it without using the workaround I mentioned. Would be nice to be able to reselect without going to 2A again unless this introduces other problems.

Comment 4 Jason Montleon 2016-12-06 02:38:28 UTC
You should be able to deselect hypervisors on 2C before returning to 2B. And then there is no need to go to 2A. Does that work?

Comment 5 Julie 2016-12-06 03:01:04 UTC
I will need to test again, I may have progressed to 2D before going back to make the amendment.

Comment 6 James Olin Oden 2016-12-07 18:00:34 UTC
Verified in QCI-1.1-RHEL-7-20161206.t.0

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


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