Bug 1041165

Summary:	reboot does not work; system hangs
Product:	[openSUSE] openSUSE Distribution	Reporter:	Hubert Mantel <mantel>
Component:	Basesystem	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	dmaiocchi
Version:	Leap 42.2
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 42.2
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Hubert Mantel 2017-05-29 06:53:34 UTC

As every monday I installed all the pending software updates available for Leap 42.2. Since there were updates to core components such as glibc, I decided to reboot the system afterwards. But this does not work. After some minutes, I only see the blinking dots. After pressing ESC, I see that the shutdown pretends to be successful; last message on the screen is

[Ok] Reached target Shutdown

But the system will not reboot. There are no running gettys on virtual consoles any longer, so the only option left is pressing the big red button.

The journal does not contain any related error messages.

The problem cannot be reproduced, but it seems to happen in about 1 of 4 or 5 cases. At one time I let the system sit in its state for about half an hour to verify that there is no timeout like it was present in sysvinit.

Since (re-)booting the system is core functionality of an init process and it is not working reliably, this is a critical problem. Imagine performing a mass update in a data center with thousands of machines and all needing a manual reset.

Comment 1 Dario Maiocchi 2017-05-29 07:05:07 UTC

i can confirm that this bug happens to me also on intel dell leap42.1

Comment 2 Tomáš Chvátal 2018-04-17 14:10:46 UTC

This is automated batch bugzilla cleanup.

The openSUSE 42.2 changed to end-of-life (EOL [1]) status. As such
it 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 
openSUSE, or you can still observe it under openSUSE Leap 15.0, please
feel free to reopen this bug against that version (see the "Version"
component in the bug fields), or alternatively open
a new ticket.

Thank you for reporting this bug and we are sorry it could not be fixed
during the lifetime of the release.

[1] https://en.opensuse.org/Lifetime