Bug 2220954
Summary: | [RHEL 8.8] System gets hang forever during shutdown while running a stop job on luks mapped volume. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | rcheerla |
Component: | systemd | Assignee: | Michal Sekletar <msekleta> |
Status: | CLOSED MIGRATED | QA Contact: | Frantisek Sumsal <fsumsal> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.8 | CC: | asayyad, cjain, rmadhuso, tom.ty89 |
Target Milestone: | rc | Keywords: | MigratedToJIRA, Reproducer |
Target Release: | --- | ||
Hardware: | Unspecified | ||
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-21 15:19:39 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: |
Description
rcheerla
2023-07-06 16:40:53 UTC
I also noticed same issue with rhel 8.8 System reboot hangs at “A stop job is running for /dev/mapper/<luks_map_disk>" where unmounting of encrypted volume got hang at boot process. But it works fine if we power off /power on the machine. Tested with version systemd-239-68.el8_7.4.x86_64 and works fine @ Does it occur even if the filesystem on the container is not mounted before reboot? If not, please share the full, exact fstab entry, or, even better, the systemctl show output for the corresponding mount unit? (Just the Before= line would do.) 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. 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. |