Description of problem: Follow up issue from bz#1310330#C74 Once a LUN is removed from the Storage Domain, not all LVs are deactivated by vdsm on the hypervisors, other then the one that was used to remove the LUN. As the sysadmin, after the removal of the LUN, removing the multipath device with 'multipath -f "WWN"' fails since the LV's are still active. Version-Release number of selected component (if applicable): vdsm-4.19.31-1.el7ev.x86_64 How reproducible: Always Steps to Reproduce: 1. Remove the LUN / Storage Domain from RHV 2. Unexport the LUN from all hypervisors 3. On the hypervisor with the SPM role, remove the mpath device: ~~~ multipath -f "WWN" ~~~ 4. On all other hypervisors remove the mpath device using the same command Actual results: On the hypervisor with the SPM role, the mpath device can be removed successfully while on the other hypervisors the mpath removal fails because there are active LVs. As an example: lrwxrwxrwx. 1 root root 8 Feb 1 11:20 /dev/mapper/0a4f3a32--a64a--4c51--96cf--ca60c1a8393c-ids -> ../dm-72 lrwxrwxrwx. 1 root root 8 Feb 1 11:20 /dev/mapper/0a4f3a32--a64a--4c51--96cf--ca60c1a8393c-inbox -> ../dm-73 lrwxrwxrwx. 1 root root 8 Feb 1 11:20 /dev/mapper/0a4f3a32--a64a--4c51--96cf--ca60c1a8393c-leases -> ../dm-71 lrwxrwxrwx. 1 root root 8 Feb 1 11:20 /dev/mapper/0a4f3a32--a64a--4c51--96cf--ca60c1a8393c-master -> ../dm-74 lrwxrwxrwx. 1 root root 8 Feb 1 11:20 /dev/mapper/0a4f3a32--a64a--4c51--96cf--ca60c1a8393c-metadata -> ../dm-68 lrwxrwxrwx. 1 root root 8 Feb 1 11:20 /dev/mapper/0a4f3a32--a64a--4c51--96cf--ca60c1a8393c-outbox -> ../dm-69 lrwxrwxrwx. 1 root root 8 Feb 1 11:20 /dev/mapper/0a4f3a32--a64a--4c51--96cf--ca60c1a8393c-xleases -> ../dm-70 Expected results: The LVs to be deactivated on all hypervisors and the removal of the mpath device completes successfully. Additional info: Manually removing the LVs when decommissioning a LUN with "dmsetup remove" is cumbersome and error-prone. Customer uses 3Par with VLUNs but this issue should apply to any SAN.
Ron, you wrote: > 1. Remove the LUN / Storage Domain from RHV Do you mean removing a storage domain? To remove a storage domain, the storage domain must be deactivated first. When we deactivating a storage domain, we should deactivate all the LVs on that storage domain on all hosts. Is this the flow you describe in comment 0? Can you provide vdsm logs from a host that have was not used to remove the storage domain, and has leftover lvs? If you don't have such logs I guess that QE can reproduce this issue.
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
sync2jira
*** Bug 1778291 has been marked as a duplicate of this bug. ***
Hi Vojtech, Can you please provide a clear verification scenario for this bug?
(In reply to Avihai from comment #16) > Hi Vojtech, > > Can you please provide a clear verification scenario for this bug? it seems this duplicate BZ #1163890 - provided test scenarios there
(In reply to Vojtech Juranek from comment #17) > (In reply to Avihai from comment #16) > > Hi Vojtech, > > > > Can you please provide a clear verification scenario for this bug? > > it seems this duplicate BZ #1163890 - provided test scenarios there Wait, if this is a duplicate bug please close this bug as duplicate. No need to verify it again.
yes, this is duplicate of BZ #1163890 which was already verified. *** This bug has been marked as a duplicate of bug 1163890 ***