Comment 9 for bug 1765765

Revision history for this message
Brian Brunswick (brian-ithil) wrote :

Just to confirm that for me also, 18.04.2 vs 18.04.1 fixes this issue and the systemd resolver is correctly picking up the dns from the non-managed interface that resulted from the network boot with ip=dhcp.

This is using the casper images with no modification - I still have to supply either 'toram' or 'systemd.mask=dev-hugepages.mount systemd.mask=dev-mqueue.mount systemd.mask=sys-fs-fuse-connections.mount systemd.mask=sys-kernel-config.mount systemd.mask=sys-kernel-debug.mount systemd.mask=tmp.mount' to dodge round the other issues, and note that the initrd has changed name from initrd.lz to initrd between .1 and .2

Just for the record, here my pxelinux configs, for a server at ...212

label bionic2toram
        kernel ubuntu-18.04.2-desktop-amd64/casper/vmlinuz
        append initrd=ubuntu-18.04.2-desktop-amd64/casper/initrd ip=dhcp toram boot=casper netboot=nfs nfsroot=192.168.10.212:/netboot/ubuntu-18.04.2-desktop-amd64

label bionic2
        kernel ubuntu-18.04.2-desktop-amd64/casper/vmlinuz
        append initrd=ubuntu-18.04.2-desktop-amd64/casper/initrd ip=dhcp boot=casper netboot=nfs nfsroot=192.168.10.212:/netboot/ubuntu-18.04.2-desktop-amd64 systemd.mask=dev-hugepages.mount systemd.mask=dev-mqueue.mount systemd.mask=sys-fs-fuse-connections.mount systemd.mask=sys-kernel-config.mount systemd.mask=sys-kernel-debug.mount systemd.mask=tmp.mount