RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1437107 - initrd-cleanup.service gets started and fails after Crash dump
Summary: initrd-cleanup.service gets started and fails after Crash dump
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kexec-tools
Version: 7.3
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Xunlei Pang
QA Contact: Qiao Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-29 13:54 UTC by Daniel Borek
Modified: 2021-03-11 15:05 UTC (History)
6 users (show)

Fixed In Version: kexec-tools-2.0.14-7.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 09:33:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2300 0 normal SHIPPED_LIVE kexec-tools bug fix and enhancement update 2017-08-01 12:40:58 UTC

Description Daniel Borek 2017-03-29 13:54:35 UTC 
Description of problem:

Whenever we take crash dump and kdump completes saving vmcore, there is number of services that get stopped successfully and just before system reboots the initrd-cleanup.service starts. The service fails and the system continues regardless, rebooting within fraction of a second.
This causes customer concern and perhaps we don't actually need the service. It merely isolates root switch which probably isn't necessary given system is going down anyway. 

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


How reproducible:

100% reproducible on customer's system and my virtualbox instance.

Steps to Reproduce:
1. Install 7.3 and configure kdump.
2. Run echo c > /proc/sysrq-trigger
3. Watch the console, message about failed service appears for split second and system reboots.

Actual results:

Here's console log:
makedumpfile Completed.
kdump: saving vmcore complete
[  OK  ] Stopped target Timers.
[  OK  ] Stopped dracut pre-udev hook.
         Stopping dracut pre-udev hook...
[  OK  ] Stopped dracut cmdline hook.
         Stopping dracut cmdline hook...
[  OK  ] Stopped Kdump Vmcore Save Service.
[  OK  ] Stopped dracut pre-pivot and cleanup hook.
         Stopping dracut pre-pivot and cleanup hook...
[  OK  ] Stopped target Remote File Systems.
[  OK  ] Stopped target Remote File Systems (Pre).
[  OK  ] Stopped target Initrd Default Target.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped target Sockets.
[  OK  ] Stopped target System Initialization.
[  OK  ] Stopped Create Static Device Nodes in /dev.
         Stopping Create Static Device Nodes in /dev...
[  OK  ] Stopped target Local File Systems.
[  OK  ] Stopped Apply Kernel Variables.
         Stopping Apply Kernel Variables...
[  OK  ] Reached target Shutdown.
[  OK  ] Stopped target Swap.
[  OK  ] Stopped target Slices.
[  OK  ] Stopped target Initrd Root File System.
         Unmounting /sysroot...
[  OK  ] Stopped target Initrd File Systems.
         Starting Cleaning Up and Shutting Down Daemons...
[  OK  ] Stopped dracut initqueue hook.
         Stopping dracut initqueue hook...
[FAILED] Failed to start Cleaning Up and Shutting Down Daemons.
See 'systemctl status initrd-cleanup.service' for details.
[  182.377630] XFS (dm-0): Unmounting Filesystem
[  OK  ] Unmounted /sysroot.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Reached target Final Step.
         Starting Reboot...
[  182.489395] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[  182.494431] systemd-journald[89]: Received SIGTERM from PID 1 (systemd-shutdow).
[  182.498188] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[  182.502688] systemd-shutdown[1]: Unmounting file systems.
[  182.505126] systemd-shutdown[1]: All filesystems unmounted.
[  182.507459] systemd-shutdown[1]: Deactivating swaps.
[  182.509555] systemd-shutdown[1]: All swaps deactivated.
[  182.511820] systemd-shutdown[1]: Detaching loop devices.
[  182.514110] systemd-shutdown[1]: All loop devices detached.
[  182.516406] systemd-shutdown[1]: Detaching DM devices.
[  182.518571] systemd-shutdown[1]: Detaching DM 253:0.
[  182.522985] systemd-shutdown[1]: All DM devices detached.
[  182.525434] systemd-shutdown[1]: Rebooting.



Expected results:
initrd-cleanup.service to not be called if it's unnecessary or to start cleanly if it's truly needed at this stage.


Additional info:
Comment 2 Xunlei Pang 2017-04-17 08:10:18 UTC 
Fedora commit b2534348199a("use "systemctl reboot -f" for reboot action") should be able to fix this.
Comment 8 errata-xmlrpc 2017-08-01 09:33:50 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2300
Note You need to log in before you can comment on or make changes to this bug.