Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 1193067[details]
sosreport of effected system
Description of problem:
Just using the standard reboot command causes the reboot to hang, however running these commands:
sync && reboot -f
sync && poweroff -f
Allows the reboot to complete. This suggests it is a failing in systemd
Version-Release number of selected component (if applicable):
How reproducible:
When customer initiates a reboot either from VMware (current tools are installed and hypervisor is ESXi 6.0) or from the OS (systemctl reboot) the VM goes to a black screen with a single gray cursor and just blinks forever, the system will never actually reboot. This problem happens randomly and affect all of customers RHEL 7.1 systems, customer states 2-3 reboots out of 10 will work, the others hang forever.
Steps to Reproduce:
try to reboot normally
Actual results:
system hangs at blinking curser
Expected results:
system shuts down
Additional info:
Created attachment 1193067 [details] sosreport of effected system Description of problem: Just using the standard reboot command causes the reboot to hang, however running these commands: sync && reboot -f sync && poweroff -f Allows the reboot to complete. This suggests it is a failing in systemd Version-Release number of selected component (if applicable): How reproducible: When customer initiates a reboot either from VMware (current tools are installed and hypervisor is ESXi 6.0) or from the OS (systemctl reboot) the VM goes to a black screen with a single gray cursor and just blinks forever, the system will never actually reboot. This problem happens randomly and affect all of customers RHEL 7.1 systems, customer states 2-3 reboots out of 10 will work, the others hang forever. Steps to Reproduce: try to reboot normally Actual results: system hangs at blinking curser Expected results: system shuts down Additional info: