Bug 2101793

Summary:	dmeventd needs to quit upon receiving SIGTERM
Product:	Red Hat Enterprise Linux 8	Reporter:	Renaud Métrich <rmetrich>
Component:	lvm2	Assignee:	LVM Team <lvm-team>
lvm2 sub component:	dmeventd	QA Contact:	cluster-qe <cluster-qe>
Status:	CLOSED MIGRATED	Docs Contact:
Severity:	medium
Priority:	medium	CC:	agk, heinzm, jbrassow, msnitzer, prajnoha, thornber, zkabelac
Version:	8.6	Keywords:	MigratedToJIRA, Triaged
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-23 18:34:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Zdenek Kabelac 2022-06-28 16:57:11 UTC

User is supposed to  *UNMONITOR*  LVs  before  quiting dmeventd.

'dmveventd' is protected  against signal - so processed commands which *MAY* freeze your system (i.e.  suspend devices) aren't leaving  system in unusable state.

So I'm not sure what  '--force reboot' is doing - but  it should run   'vgchange --monitor n' first.

This is not seen as bug in dmeventd -  rather some logical problem with  reboot sequence.

Comment 2 Renaud Métrich 2022-06-29 07:29:01 UTC

Hi Zdenek,

From your comment, I understand it's really necessary to go through the normal shutdown sequence, so I think there is nothing to do on this side.
Specifically here we need lvm2-monitor.service to stop, which will lead to stopping dmeventd.service as well.
This is what I see on normal shutdown:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Jun 28 10:04:36.507032 vm-thin8 systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
...
Jun 28 10:04:36.514671 vm-thin8 dmeventd[873]: dmeventd detected break while being idle for 0 second(s), exiting.
Jun 28 10:04:36.514675 vm-thin8 dmeventd[873]: dmeventd shutting down.
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Comment 4 RHEL Program Management 2023-09-23 18:21:18 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 5 RHEL Program Management 2023-09-23 18:34:59 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 6 Zdenek Kabelac 2023-09-26 20:09:09 UTC

Upstream lvm2  (2.03.23)  implemented support for allowing to TERMinate   'dmeventd'  if there is  /run/nologin file present  (should be created on shutdown by systemd).