[Bug 1171055] [Build 20200502] kdump_and_crash: Failed to start Switch Root
http://bugzilla.suse.com/show_bug.cgi?id=1171055 http://bugzilla.suse.com/show_bug.cgi?id=1171055#c8 --- Comment #8 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Thomas Blume from comment #7)
That looks suspicious:
--> # rpm -q kdump kdump-0.9.0-13.1.x86_64 # mkdumprd -f Regenerating kdump initrd ... dracut: Executing: /usr/bin/dracut --force --hostonly --omit "plymouth resume usrmount" "--compress=xz -0 --check=crc32" --add kdump /boot/initrd-5.6.8-1-default-kdump 5.6.8-1-default [...] dracut: *** Including module: kdump *** ln: failed to create symbolic link '/var/tmp/dracut.3o3Ldx/initramfs//usr/lib/systemd/system/initrd.target. wants/kdump-save.service': No such file or directory
Argh, it is actually caused by a change in dracut! dracut-0.50 ships a rootfs-generator that creates the initrd.target.wants directory on the fly: --> /usr/lib/dracut/modules.d/98dracut-systemd/rootfs-generator.sh: [ -d "$GENERATOR_DIR"/initrd.target.wants ] || mkdir -p "$GENERATOR_DIR"/initrd.target.wants --< So initrd.target.wants is not present at initrd creation time and the symlink creation for kdump-save.service fails. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com