Bug 1778291 - Default logical volumes are not deactivated from all the hosts while removing the storage domain
Summary: Default logical volumes are not deactivated from all the hosts while removing...
Keywords:
Status: CLOSED DUPLICATE of bug 1544370
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.3.6
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Avihai
URL:
Whiteboard:
Depends On:
Blocks: 902971
TreeView+ depends on / blocked
 
Reported: 2019-11-29 18:47 UTC by nijin ashok
Modified: 2023-03-24 16:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-17 13:35:22 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:
lsvaty: testing_plan_complete-


Attachments (Terms of Use)

Description nijin ashok 2019-11-29 18:47:04 UTC
Description of problem:

While removing the storage domain with the option "format storage domain", the RHV only does vgremove and pvremove from the "use host". However, it doesn't deactivate the LVs in the other host leaving the active LVs in the device-mapper table. The user has to manually remove all of these active LVs to remove the LUN from the multipath layer.

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

rhvm-4.3.6.7-0.1.el7.noarch

How reproducible:

100%

Steps to Reproduce:

1. Detach the storage domain from the environment. However, this will not decativates any of the LVs in any host.

dhcp0-5 ~]# dmsetup ls |grep bb696594
bb696594--e63b--4559--91a8--b7339d054ab2-master	(253:10)
bb696594--e63b--4559--91a8--b7339d054ab2-outbox	(253:5)
bb696594--e63b--4559--91a8--b7339d054ab2-xleases	(253:6)
bb696594--e63b--4559--91a8--b7339d054ab2-ids	(253:8)
bb696594--e63b--4559--91a8--b7339d054ab2-inbox	(253:9)
bb696594--e63b--4559--91a8--b7339d054ab2-leases	(253:7)
bb696594--e63b--4559--91a8--b7339d054ab2-metadata	(253:4)

2. Remove the storage domain with the "format" option. The LVs are deactivated only in the host which is used for format as a part of vgremove process however the devices still exist in all other hosts.

The host used for format.

dhcp0-5 ~]# dmsetup ls |grep bb696594
            <-- empty output -->

Another host in DC.

dhcp0-2 ~]# dmsetup ls |grep bb696594
bb696594--e63b--4559--91a8--b7339d054ab2-master	(253:10)
bb696594--e63b--4559--91a8--b7339d054ab2-outbox	(253:7)
bb696594--e63b--4559--91a8--b7339d054ab2-xleases	(253:8)
bb696594--e63b--4559--91a8--b7339d054ab2-ids	(253:5)
bb696594--e63b--4559--91a8--b7339d054ab2-inbox	(253:9)
bb696594--e63b--4559--91a8--b7339d054ab2-leases	(253:6)
bb696594--e63b--4559--91a8--b7339d054ab2-metadata	(253:4)


3. The user can't even deactivate these devices by "lvm" commands since the VG and PV are already removed. The only option is to individually delete each device using dmsetup command.

Actual results:

Default logical volumes are not deactivated from all the hosts while removing the storage domain  

Expected results:

All the LVs should be deactivated in all the host when the storage domain is put into maintenance mode or atleast when it's detached. Leaving these LVs in the device mapper table leaves huge effort to the administrator to clean up the LUN as a part of the removal process as the user has to use "dmsetup" commands to remove each device from each host.


Additional info:

Comment 1 Marina Kalinin 2019-12-09 16:43:19 UTC
Nijin, KCS please?
Would this be good enough or requires modification? https://access.redhat.com/solutions/129983

Comment 2 nijin ashok 2019-12-17 13:35:22 UTC

*** This bug has been marked as a duplicate of bug 1544370 ***


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