(In reply to Martin Wilck from comment #25) > if you install both a new kernel and some other > package that wants to rebuild the initrd at the same time, no initrd will > be built at all. Makes sense, except, I'm doing single transaction in each instance: rpm. All installations here have this configuration: # zypper ll | grep kern 25 | kernel-de* | package | (any) | 26 | kernel-lo* | package | (any) | # > So finally some clue ... Yay!!!!! Seems right this issue would have started roughly the same time as SKIP_REGENERATE_INITRD_ALL was introduced on account of bug 1192014 last spring. Given how hard this is to reproduce, I'd expect it to take more than a month for that new regenerate-initrd-posttrans to suggest this is fixed, trying to prove something won't or can't happen, and assuming another suse-module-tools-scriptlets update doesn't replace it before enough time passes.