Comment # 3 on bug 1228929 from Felix Miata

Created attachment 876539 [details]
host p5bse tw20240806 /var/log/zypper.log-20240807.xz

Don't forget, zypper was not used for kernel installation. Comment #0 is full
terminal log, minus some irrelevant command output marked with "...", and minus
typing errors. It's the whole session beginning after zypper dup completed.
/etc/zypp/locks includes kernel-de* and kernel-lo*, as is standard procedure
here. The comment #0 sequence of events was planned based upon the several
failures on other TW hosts (and possibly also on Slowroll hosts). 

(In reply to Martin Wilck from comment #2)
> I can't reproduce this. initrds were created just fine here. I notice that
> your kernel version is older than current TW, and that the previously
> installed kernel was pretty old (6.1.12). Is this slowroll?

Not Slowroll. 6.1.12 was removed to free space prior to 6.8.9 installation.
Comment #0 shows newest initrd prior to that for 6.8.9 is for 6.7.9.

> Anyway, please provide the zypper.log file (the part that corresponds to the
> transaction shown in the journal).

zypper.log was already rolled, so the entirety of zypper.log-20240807.xz is
attached. Prior is zypper.log-20240806.xz last date contained is 14 June, as is
its file timestamp.

Later same day I upgraded to 20240806 32bit on host gx270 using the same
sequence of events as shown in comment #0, and initrd was generated in normal
fashion expected. As I wrote in comment #0: "It only occurs on a random basis."

I still have more TW installations that need upgrades and newer kernels, so
will be trying more reproductions using same scenario.