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.

Created attachment 1144191 [details]
dracut emergency shell

Description of problem:
I am using a kernel image with the "reencrypt" option to reencrypt a harddrive during first setup. The kernel does the reencrypt, and than drops into the dracut emergency shell. The only way to reboot from this shell is to press the Power button for 8 seconds to power down the notebook

Version-Release number of selected component (if applicable):
dracut-033-360.el7_2.x86_64.rpm

How reproducible:
Every time you enter the dracut Emergency shell

Steps to Reproduce:
1. enter the dracut emergency shell
2. try to reboot in different ways than powering off the notebook:
2.a type: reboot
2.b type: logout
2.c press "Ctrl-d"

Actual results:
Screen turns into plymouth screen and stays there without doing anything

Expected results:
Computer should reboot

Additional info:
It would be also great to have a grub kernel option for a auto reboot. Like in my current case.. i am using "grub2-reboot 1" to start the reencrypt kernel only once.. than i need a reboot to start the original kernel. If I could tell the reencrypt kernel to reboot automatically when entering the Emergency shell, it would make the process even easier.

reboot should work with:

http://people.redhat.com/harald/downloads/dracut/dracut-033-436.el7/

Reproduced on dracut-033-359. Verified on dracut-033-450. System rebooted without issues.

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://rhn.redhat.com/errata/RHBA-2016-2530.html