Bug 1227745 - Tumbleweed 20240712 dracut loop
Summary: Tumbleweed 20240712 dracut loop
Status: RESOLVED INVALID
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: Other openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-14 20:16 UTC by Georg Pfuetzenreuter
Modified: 2024-07-14 22:00 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
/var/log/zypp/history (169.37 KB, text/plain)
2024-07-14 20:24 UTC, Georg Pfuetzenreuter 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Georg Pfuetzenreuter 2024-07-14 20:16:36 UTC 
Hi,

on one of our machines `dup` installed this today:

```
The following 25 packages are going to be upgraded:
  ca-certificates-mozilla coreutils coreutils-doc coreutils-systemd gio-branding-openSUSE glib2-tools libgio-2_0-0 libglib-2_0-0 libgmodule-2_0-0
  libgobject-2_0-0 libselinux1 libsemanage-conf libsemanage2 libsepol2 openSUSE-release openSUSE-release-ftp python3-mailman-web python311-Django python311-zipp
  python312-Django python312-zipp typelib-1_0-GLib-2_0 typelib-1_0-GModule-2_0 typelib-1_0-GObject-2_0 typelib-1_0-Gio-2_0

The following product is going to be upgraded:
  openSUSE Tumbleweed  20240709-0 -> 20240712-0
```

It's known that the initrd tends to rebuild multiple times during an upgrade.
But this time it seemed to be stuck in a loop - after 22 times of `Executing: /usr/bin/dracut --kver=6.7.1-1-default -f` I aborted with Ctrl-c:

```
^C
Trying to exit gracefully...
Segmentation fault (core dumped)
```

Any ideas?
Comment 1 Georg Pfuetzenreuter 2024-07-14 20:24:01 UTC 
Created attachment 876044 [details]
/var/log/zypp/history
Comment 2 hui 2024-07-14 20:44:13 UTC 
Is it intended that you have 21 kernels installed on this machine? Did you intentionelly disable the purge-kernels.service?
Comment 3 Georg Pfuetzenreuter 2024-07-14 22:00:00 UTC 
Thank you for the pointer - `zypper purge-kernels` removed 34 kernels. It seems `purge-kernels-service` is not installed, I will repair that.