Description of problem: The Cockpit workflow for hosted-engine has a typo. Please correct "fiber channel" as "fibre channel" as shown here https://gerrit.ovirt.org/#/c/95150/
Test Version RHVH-4.2-20181026.0-RHVH-x86_64-dvd1.iso cockpit-bridge-176-3.el7.x86_64 cockpit-storaged-176-3.el7.noarch cockpit-176-3.el7.x86_64 cockpit-ovirt-dashboard-0.11.37-1.el7ev.noarch cockpit-system-176-3.el7.noarch cockpit-ws-176-3.el7.x86_64 cockpit-machines-ovirt-176-3.el7.noarch cockpit-dashboard-176-3.el7.x86_64 ovirt-hosted-engine-setup-2.2.30-1.el7ev.noarch ovirt-hosted-engine-ha-2.2.18-1.el7ev.noarch Test Steps: 1. Clean install RHVH-4.2-20181026.0-RHVH-x86_64-dvd1.iso 2. During Deploy hosted-engine, when selecting the storage type 3. Check the name of Fibre Channel Result: "fiber channel" is shown instead of "fibre channel". QE can reproduce this issue, change flag testing_ack to "+"
Retest with RHVH 4.2.8 latest build rhvh-4.2.8.0-0.20181212.0, still can be reproduced.
Test Version redhat-virtualization-host-4.2-20190108.0.el7_6.x86_64.liveimg.squashfs cockpit-176-4.el7.x86_64 cockpit-system-176-4.el7.noarch cockpit-ws-176-4.el7.x86_64 cockpit-machines-ovirt-176-4.el7.noarch cockpit-ovirt-dashboard-0.11.38-1.el7ev.noarch cockpit-dashboard-176-4.el7.x86_64 cockpit-bridge-176-4.el7.x86_64 cockpit-storaged-176-4.el7.noarch ovirt-hosted-engine-setup-2.2.33-1.el7ev.noarch ovirt-hosted-engine-ha-2.2.19-1.el7ev.noarch Test Steps: 1. Clean install redhat-virtualization-host-4.2-20190108.0.el7_6.x86_64.liveimg.squashfs via kickstart file 2. During Deploy hosted-engine, when selecting the storage type 3. Check the name of Fibre Channel Result: "fibre channel" is shown. Bug is fixed already, QE will change status to "VERIFIED" after it move to "ON_QA"
Change bug status to "VERIFIED" according to comment 4
This bugzilla is included in oVirt 4.2.8 release, published on January 22nd 2019. Since the problem described in this bug report should be resolved in oVirt 4.2.8 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.