Comment # 1 on bug 1170842 from Thomas Blume

(In reply to Alberto Planas Dominguez from comment #0)
> Created attachment 837097 [details]
> Dracut logs
> 
> When booting a OEM Kiwi via PXE boot, the download of the second kernel,
> initrd and image fails.
> 
> Inside the dracut shell we can see that the device have two interfaces, but
> only the first interface gets up. The second one can be manually up via
> "ifup enp0s2"
> 
> The logs shows that indeed, there is only one call to ifup, that correspond
> to the first interface.

If not explicitly given at the command line, dracut will only set up one
interface and just continue if this is successfull, which is the case here:

-->
   39.785787] localhost dracut-initqueue[575]: + ip -4 addr add 10.0.3.101/24
broadcast 10.0.3.255 dev enp0s1
[   39.856029] localhost dracut-initqueue[575]: + route=()
[   39.858205] localhost dracut-initqueue[575]: + local r route
[   39.858205] localhost dracut-initqueue[575]: + '[' -n '' ']'
[   39.858205] localhost dracut-initqueue[575]: + local g
[   39.858205] localhost dracut-initqueue[575]: + '[' -n 10.0.3.101 ']'
[   39.858205] localhost dracut-initqueue[575]: + for g in ${GATEWAYS}
[   39.858205] localhost dracut-initqueue[575]: + ip -4 route add default via
10.0.3.101 dev enp0s1
[   39.898801] localhost dracut-initqueue[575]: + break
[   39.901409] worker dracut-initqueue[575]: + '[' -n '' ']'
[   39.901409] worker dracut-initqueue[575]: + '[' -n worker ']'
[   39.901409] worker dracut-initqueue[575]: + echo worker
[   39.901409] worker dracut-initqueue[575]: + '[' '!' -s
/tmp/net.enp0s1.resolv.conf.ipv4 ']'
[   39.907099] worker dracut-initqueue[575]: + '[' -n '' ']'
[   39.907099] worker dracut-initqueue[575]: + '[' -n '' ']'
[   39.907099] worker dracut-initqueue[575]: + '[' -n 10.0.3.1 ']'
[   39.907099] worker dracut-initqueue[575]: + for s in ${DNSSERVERS}
[   39.907099] worker dracut-initqueue[575]: + echo nameserver 10.0.3.1
[   39.907099] worker dracut-initqueue[575]: + '[' -e
/tmp/net.enp0s1.resolv.conf.ipv4 ']'
[   39.907099] worker dracut-initqueue[575]: + '[' '!' -e /etc/resolv.conf ']'
[   39.907099] worker dracut-initqueue[575]: + cp -f
/tmp/net.enp0s1.resolv.conf.ipv4 /etc/resolv.conf
[   39.945505] worker systemd[1]: inotify event for /etc/localtime
[   39.949340] worker systemd[1]: Failed to stat /etc/localtime, ignoring: No
such file or directory
[   39.951267] worker dracut-initqueue[575]: + info 'DHCP is finished
successfully'
[   39.953333] worker dracut-initqueue[575]: + echo 'DHCP is finished
successfully'
--<

The root cause visible in the logs is that the device for installation isn't
found:

-->
[   48.582317] worker dracut-pre-mount[719]:
/////lib/dracut/hooks/pre-mount/30-kiwi-dump-image.sh@15(report_and_quit): die
'No device(s) for installation found'
[   48.582317] worker dracut-pre-mount[719]: ////lib/dracut-lib.sh@460(die):
echo '<24>dracut: FATAL: No device(s) for installation found'
[   48.582317] worker dracut-pre-mount[719]: ////lib/dracut-lib.sh@461(die):
echo '<24>dracut: Refusing to continue'
[   48.582317] worker dracut-pre-mount[719]: ////lib/dracut-lib.sh@465(die):
echo 'warn dracut: FATAL: "No device(s) for installation found"'
[   48.582317] worker dracut-pre-mount[719]: ////lib/dracut-lib.sh@466(die):
echo 'warn dracut: Refusing to continue'
--<

Still, I can see that a device gets plugged:

-->
[   36.297674] localhost systemd[1]: dev-vda.device: Changed dead -> plugged
[   36.298760] localhost systemd[1]:
sys-devices-platform-LNRO0005:1f-virtio2-block-vda.device: Changed dead ->
plugged
--<

Is vda the device configured for installation?