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

Bug 1997609

Summary:

hosted engine host is not able to deactivate hosted_storage SD volume group because he_sanlock volume is being used

Product:

Red Hat Enterprise Virtualization Manager

Reporter:

Marian Jankular <mjankula>

Component:

vdsm

Assignee:

Asaf Rachmani <arachman>

Status:

CLOSED DUPLICATE

QA Contact:

meital avital <mavital>

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

4.4.6

CC:

arachman, fdelorey, jortialc, lsurette, srevivo, ycui

Target Milestone:

ovirt-4.4.9

Keywords:

ZStream

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-10-04 07:49:17 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

Integration

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
logs from reproducer	none

Description Marian Jankular 2021-08-25 14:05:53 UTC

Description of problem:
hosted engine host is not able to deactivate hosted_storage SD volume group  because he_sanlock volume is being used

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

customer attempted to upgrade one of the host and experienced this twice already

Actual results:
upgrade failed because the vg/lv is not deactivated

Expected results:
successful upgrade

Additional info:

Comment 6 Marian Jankular 2021-09-23 12:25:12 UTC

I was able to reproduce the issue:

1, deploy hosted engine on rhvh4.4.7 on fc lun (fake fc in my case)
2, add the second host with hosted-engine deploy option
3, put hosted engine to global maintenance
4, put 2nd host to the maintenance

2nd host is not able to deactivate the lockspace lv:
~~~
2021-09-23 12:12:52,585+0000 WARN  (monitor/63c4a56) [storage.LVM] All 1 tries have failed: LVM command failed: 'cmd=[\'/sbin/lvm\', \'vgchange\', \'--config\', \'devices {  preferred_names=["^/dev/mapper/"]  ignore_suspended_devices=1  write_cache_state=0  disable_after_error_count=3  filter=["a|^/dev/mapper/0QEMU_QEMU_HARDDISK_hosted_storage$|", "r|.*|"]  hints="none"  obtain_device_list_from_udev=0 } global {  locking_type=1  prioritise_write_locks=1  wait_for_locks=1  use_lvmetad=0  use_lvmpolld=1 } backup {  retain_min=50  retain_days=0 }\', \'--available\', \'n\', \'63c4a566-ebcb-4683-9058-533f44a7da4a\'] rc=5 out=[] err=[\'  Logical volume 63c4a566-ebcb-4683-9058-533f44a7da4a/0e5bffe5-379b-4b48-a98c-87eb0ceaff61 in use.\', \'  Can\\\'t deactivate volume group "63c4a566-ebcb-4683-9058-533f44a7da4a" with 1 open logical volume(s)\']' (lvm:561)
2021-09-23 12:12:52,585+0000 INFO  (monitor/63c4a56) [storage.LVM] Error deactivating VG 63c4a566-ebcb-4683-9058-533f44a7da4a: cmd=['/sbin/lvm', 'vgchange', '--config', 'devices {  preferred_names=["^/dev/mapper/"]  ignore_suspended_devices=1  write_cache_state=0  disable_after_error_count=3  filter=["a|^/dev/mapper/0QEMU_QEMU_HARDDISK_hosted_storage$|", "r|.*|"]  hints="none"  obtain_device_list_from_udev=0 } global {  locking_type=1  prioritise_write_locks=1  wait_for_locks=1  use_lvmetad=0  use_lvmpolld=1 } backup {  retain_min=50  retain_days=0 }', '--available', 'n', '63c4a566-ebcb-4683-9058-533f44a7da4a'] rc=5 out=[] err=['  Logical volume 63c4a566-ebcb-4683-9058-533f44a7da4a/0e5bffe5-379b-4b48-a98c-87eb0ceaff61 in use.', '  Can\'t deactivate volume group "63c4a566-ebcb-4683-9058-533f44a7da4a" with 1 open logical volume(s)'] (lvm:1536)
~~~
5, reboot the host
6, once the host will be rebooted the ovirt-ha-agent and ovirt-ha-broker are constantly stopping and restarting
in my environment agent got to the restart count 63 and after that issue stopped.

Will attach logs from reproducer.

Comment 7 Marian Jankular 2021-09-23 12:29:23 UTC

Created attachment 1825628 [details]
logs from reproducer

Comment 9 Asaf Rachmani 2021-10-04 07:49:17 UTC


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