Bug ID | 1194199 |
---|---|
Summary | zypper dup on multiple HPE servers freezes, resulting system will not start |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | 64bit |
OS | openSUSE Tumbleweed |
Status | NEW |
Severity | Major |
Priority | P5 - None |
Component | Upgrade Problems |
Assignee | screening-team-bugs@suse.de |
Reporter | bob@muhlenberg.edu |
QA Contact | jsrain@suse.com |
Found By | --- |
Blocker | --- |
Created attachment 854887 [details]
Rapidly scrolling errors after startup, post fozen zypper dup
On two different HPE DL-380 and DL-360 ( Gen 8 and Gen 9 ) servers I performed
zypper dup and after installing perhaps half of the packages, the zypper dup
stalls and the system becomes unresponsive. The system looses network
connectivity and appears to be frozen. After waiting a long time ( a day ) we
rebooted the system, on booting the system boots through GRUB and after a few
seconds haangs ( usually at a green "three dots" screen ).
On booting via Advanced Options --> Recovery
It is observed various dracut errors a couple seconds into startup, followed by
a continuous stream of errors about 10 a second:
dracut-initqueue[PID]: udevadm: error while loading shared libraries:
libsystemd-shared-246.so cannot open shared object file: no such file or
directory
This scrolls continuously with a new PID on every line. This never ends and
the system is non-responsive.
I am going to attempt to do an in place upgrade with the latest DVD ISO.
In both instances the prior release installed was old ( 2020 or early 2021
vintage? ).
If this is a known issue is there a way to recoup the system? If not, what do
you need, log wise? Given this is two different physical systems and two
different prior releases, it may be a serious issue. The first time I saw
this was about 2 weeks ago.