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: | NEW --- | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | agk, heinzm, jbrassow, msnitzer, prajnoha, thornber, zkabelac |
| Version: | 8.6 | Keywords: | Triaged |
| Target Milestone: | rc | ||
| 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: | 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
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< -------- |