Bug 1567908 - [RHHI] Multipath device shown up during reboot on RHVH platform [NEEDINFO]
Summary: [RHHI] Multipath device shown up during reboot on RHVH platform
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: Documentation
Version: rhhiv-1.5
Hardware: x86_64
OS: Linux
Target Milestone: ---
: ---
Assignee: Anjana Suparna Sriram
: 1573554 (view as bug list)
Depends On: 1016535
TreeView+ depends on / blocked
Reported: 2018-04-16 12:13 UTC by bipin
Modified: 2020-12-09 12:44 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The vdsm service makes various configuration changes after Red Hat Virtualization is first installed. One such change made multipath entries for devices visible in Red Hat Hyperconverged Infrastructure for Virtualization, including local devices. This caused issues on hosts that were updated or rebooted before the Red Hat Hyperconverged Infrastructure for Virtualization deployment process was complete. Red Hat Hyperconverged Infrastructure for Virtualization now provides the option to blacklist multipath devices, which prevents any entries from being used by RHHI for Virtualization.
Clone Of:
Last Closed: 2020-12-09 12:44:45 UTC
Target Upstream Version:
rbarry: needinfo? (nlevy)

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4518231 0 None None None 2019-10-21 22:04:29 UTC

Description bipin 2018-04-16 12:13:31 UTC
Description of problem:
After a reboot on a host which is provisioned with a RHV-H, the multipath devices are shown up. This is seen only on RHV-H host. 

Version-Release number of selected component (if applicable):

How reproducible:
Most of the time

Steps to Reproduce:
1. Install RHV-H 
2. Reboot the system

Actual results:
Seeing multipath devices

Expected results:
Shouldn't see the multipath device 

Additional info:

Comment 2 Sahina Bose 2018-05-16 11:27:54 UTC
*** Bug 1573554 has been marked as a duplicate of this bug. ***

Comment 3 Doron Fediuck 2018-05-21 07:33:37 UTC
Id this RHVH specific or shows on RHEL as well?

Comment 4 bipin 2018-05-21 07:40:20 UTC

This was not seen in RHEL only in RHVH

Comment 5 Sahina Bose 2018-05-30 05:51:19 UTC
Ryan, is this related to the vdsm multipath bug 1016535 or specific to RHV-H?

Comment 6 Ryan Barry 2018-05-30 11:22:51 UTC
This is definitely related to the vdsm bug.

We configure vdsm at first boot on RHVH. If "vdsm-tool configure --force" on RHEL results in the same behavior, it's the vdsm bug. RHVH does not otherwise modify multipath

Comment 10 SATHEESARAN 2018-06-28 06:11:40 UTC
When the RHVH is installed, and then redhat-virtualization-host-image-upate rpms is installed and the node is rebooted, the multipath entries shows up for all the disks.

This is kind of nasty experience. Raising the severity to Urgent

Comment 11 Sahina Bose 2018-06-28 06:32:01 UTC
Freddy, this bug is dependent on bug 1380272. Is there a fix possible in vdsm for 4.2.5?

Comment 12 SATHEESARAN 2018-07-18 12:33:45 UTC
Workaround for this issue
1. Blacklist all the devices in /etc/multipath.conf

Add the following to the /etc/multipath.con

blacklist {
        devnode "*"

2. Reboot the RHVH hosts

One problem that I observed is that mpath names on the boot disks are not going away.

Comment 16 John Call 2019-05-28 15:36:28 UTC
In an RHHI environment (no SAN / iSCSI storage) it should be safe to simply run "ansible rhhi-hosts -a 'multipath -F'" and then relaunch the wizard.  Even better if the installation playbooks did this automatically for our customers.

Comment 27 SATHEESARAN 2020-07-23 10:32:37 UTC
With RHHI-V 1.8 'blacklist gluster devices' option is introduced with deployment
and this helps to blacklist the devices used for gluster bricks.

So these devices should not have multipath names post reboot

Should we close this bug ?

Comment 28 SATHEESARAN 2020-12-09 12:44:45 UTC
With RHHI-V 1.8 has an option to blacklist gluster brick devices, which helps to blocklist the local devices

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