Comment # 3 on bug 1171137 from David Cassany

Hi Piotr,

Thanks much for your feedback. I think the difference between your setup and
mine is the initrd creation system. In KIWI v9.x we already moved to dracut
initrds instead of the legacy custom initrds that are created by KIWI.

Could you share the `<type>` section of your image? I think you are using the
legacy initrd creation system, so you may have something like
`boot="oemboot/suse-xxx"` in your "<type>" section. If so, next question is
which initrd image descriptions are you using (as we are not providing Leap
oemboot descriptions anymore). I did a quick run of `oemboot/suse-tumbleweed`
and I did not see this problem. The boot descriptions we provide and support
are included in `kiwi-boot-descriptions` package.

> also: tried to look at bsc#1135762 but it looks like I have no right to read
> this bug ?

Sorry, my bad, this is not a public report. In any case this is a similar issue
in which we changed the boot code to run

udevadm control --reload
udevadm trigger --type=subsystems --action=add
udevadm trigger --type=devices --action=add

when retriggering udev daemon. Pretty similar to what you did.