Description of problem: The hosted engine wizard in Cockpit is functional, but UX wise a bit rough. Two new designs were suggested, one of them should be implemented to improve the UX.
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
*** Bug 1462003 has been marked as a duplicate of this bug. ***
https://www.ovirt.org/develop/release-management/features/sla/cockpit-he-wizard-ui-update/
Can this be moved to MODIFIED, or are there additional patches needed?
I was planning on moving it to MODIFIED once the validation patch [1] is merged. [1] https://gerrit.ovirt.org/#/c/82633/
(In reply to Phillip Bailey from comment #9) > I was planning on moving it to MODIFIED once the validation patch [1] is > merged. > > [1] https://gerrit.ovirt.org/#/c/82633/ And now?
Done!
Due to the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1509775, so need to assigned. For the upstream build: ovirt-node-ng-4.2.0-0.20171031.0+1, I cannot found the changes for process of deploying HostedEngine.Could you help to check?
The changes will be in the cockpit-ovirt-dashboard package. The build of node you're referencing may not have the updated package included. If the old wizard is being displayed, this is definitely the case.
QE will verify this bug if the new build is available, and the bug 1516121, 1516113 should be verified before.
Now HostedEngine use alt2 wizard UI. Test version: cockpit-ovirt-dashboard-0.11.1-0.6.el7ev.noarch rhvh-4.2.0.5-0.20171123.0+1 ovirt-host-4.2.0-0.1.master.el7ev.noarch ovirt-host-deploy-1.7.0-0.2.master.git24e53fd.el7ev.noarch ovirt-hosted-engine-setup-2.2.0-0.4.master.git0b67c21.el7ev.noarch rhvm-appliance-4.2-20171102.0.el7.noarch Test steps: 1. Clean install rhvh-4.2.0.5-0.20171123.0+1 2. Upgrade the cockpit-ovirt-dashboard pkg to cockpit-ovirt-dashboard-0.11.1-0.6.el7ev.noarch 3. Deploy the HostedEngine Actual results: HostedEngine use alt2 wizard UI. So, change this bug's status to verified.
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.