Description of problem: ------------------------ when expanding the volume from the web console ( cockpit ) as part of day2 operation, warning note is seen with the device name changed to /dev/sdx, asking to use device name with format /dev/mapper/<WWID> even with blacklist gluster device checkbox enabled Version-Release number of selected component (if applicable): ------------------------------------------------------------- cockpit-ovirt-dashboard-0.14.9.el8rhgs RHHI-V 1.8 RHGS 3.5.2 How reproducible: ------------------ Always Steps to Reproduce: -------------------- 1. Deploy RHHI-V 2. Choose the option to expand the volume from web console ( cockpit ) as part of 'Manager Gluster' button 3. On the bricks tab, change the device name from /dev/sdb to /dev/sdX Actual results: ---------------- Warning pops up asking to use device name of the format /dev/mapper/<WWID> It may confuse the customers Expected results: ------------------ No error to be reported Additional info: --- Additional comment from RHEL Program Management on 2020-07-14 05:05:57 UTC --- This bug is automatically being proposed for RHHI-V 1.8 release at Red Hat Hyperconverged Infrastructure for Virtualization product, by setting the release flag 'rhiv‑1.8' to '?'. If this bug should be proposed for a different release, please manually change the proposed release flag. --- Additional comment from SATHEESARAN on 2020-07-14 05:07:35 UTC --- Marking this bug for known issue. So workaround here is to 'ignore' this error and proceed to next step of deployment and complete the action. This warning is not legitimate. This error happens only with expand volume operation.
Tested with cockpit-ovirt-dashboard-0.14.11. 1. Expand the existing volume from cockpit 2. While updating the disk, there is no error message seen
This bugzilla is included in oVirt 4.4.2 release, published on September 17th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.2 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.