| Summary: | RHV hypervisor+engine deployment- Allow reselecting nodes at 2B after proceeding to 2C and then going back to 2B | ||
|---|---|---|---|
| Product: | Red Hat Quickstart Cloud Installer | Reporter: | Julie <juwu> |
| Component: | WebUI | Assignee: | cchase |
| Status: | CLOSED ERRATA | QA Contact: | James Olin Oden <joden> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.0 | CC: | jmontleo, joden, qci-bugzillas |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | 1.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-02-28 01:41:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Julie
2016-12-01 02:29:55 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. (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. 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? I will need to test again, I may have progressed to 2D before going back to make the amendment. Verified in QCI-1.1-RHEL-7-20161206.t.0 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 |