Hide Forgot
Created attachment 1203999 [details] The screenshot of 'shutdown -H now' Description of problem: The recommended way of dropping shell during shutdown, described at https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#debugging-dracut doesn't work: After creating /run/initramfs/etc/cmdline.d/debug.conf dracut can not read it and does not give a shell during shutdown process Version-Release number of selected component (if applicable): dracut-044-20.fc24.x86_64 kernel-4.7.4-200.fc24.x86_64 selinux-policy-3.13.1-191.16.fc24.noarch selinux-policy-targeted-3.13.1-191.16.fc24.noarch How reproducible: Always Steps to Reproduce: 1. Install F24 2. Enter the wollowing commands in the terminal window mkdir -p /run/initramfs/etc/cmdline.d echo "rd.debug rd.break=pre-shutdown rd.break=shutdown" >/run/initramfs/etc/cmdline.d/debug.conf touch /run/initramfs/.need_shutdown shutdown -H now Actual results: System haltes without dropping into shell We can see the following message on the screen: /lib/dracut-lib.sh: line 138: /etc/cmdline.d/debug.conf: Permission denied Halting reboot: System halted Expected results: dropping into shell at pre-shotdown and shutdown Additional info:
If I boot with 'enforcing=0' kernel option, then dracut gives a shell during shutdown. So it is similar to a selinux related issue.
Created attachment 1204247 [details] dracut log after 'setenforce 0' If I run 'setenforce 0' before shutdown, dracut successfully gives me the emergency shell and this is it's log How to fix selinux context in initramfs?
(In reply to Oleg Samarin from comment #2) > Created attachment 1204247 [details] > dracut log after 'setenforce 0' > > If I run 'setenforce 0' before shutdown, dracut successfully gives me the > emergency shell and this is it's log > > How to fix selinux context in initramfs? good question... reassigning to selinux-policy for advice
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.