Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1932388

Summary:	Engine doesn't deactivate VG upon block SD detach
Product:	[oVirt] ovirt-engine	Reporter:	Vojtech Juranek <vjuranek>
Component:	BLL.Storage	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED NOTABUG	QA Contact:	Avihai <aefrat>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4.4	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-25 10:05:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vojtech Juranek 2021-02-24 14:39:09 UTC

Description of problem:

When detaching block SD, SD has to be in maintenance mode. In maintenance mode, SD is disconnected from storage server and LVM VG is deactivated on the host. During detach, engine connects hosts to iscsi storage again, which results in VG activation on the hosts. During detach it disconnects from the storage server, but without deactivating VG. As a result, there are stale DM links on the hosts. This doesn't happen on host which manages SD, but on all other hosts. 

How reproducible:
Always

Steps to Reproduce:
1. create iSCSI storage domain
2. put it into maintenance
3. detach SD from the cluster

Actual results:
Stale DM links on the host.

Expected results:
No stale DM links on the host.

Additional info:
Engine connect the hosts in DetachStorageDomainFromPoolCommand.detachStorageDomain() -> connectHostsInUpToDomainStorageServer()

https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/domain/DetachStorageDomainFromPoolCommand.java#L101

Comment 1 Vojtech Juranek 2021-02-25 07:35:23 UTC

It turned out that the root cause if bug in LVM: BZ #1932761

Keeping this bug open as can be used to mitigate this issue until is fixed and gets into the RHEL.

Comment 2 Vojtech Juranek 2021-02-25 10:05:15 UTC

Closing, this is not real bug, but was a combination of misconfigured host (missing LVM filter) and LVM bug described in BZ #1932761