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
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1765765
Title:
on nfsboot 18.04 bionic, internet addresses arn't resolve properly
Status in systemd package in Ubuntu:
Confirmed
Bug description:
since ubuntu 17.10, 18.04, when i nfsboot into ubuntu live an internet
address isn't resolved properly.
i always have to put a dns server to the /etc/resolv.conf file by hand to get
address resolving to work again.
it wasn't an issue in ubuntu 16.04 and not an issue in ubuntu 17.04.
it began to be an issue starting with ubuntu 17.10 and ist still an issue now
18.04 daily-live.
the different between /etc/resolv.conf of ubuntu <=17.04 and utuntu >=17.10
is, that now only one entry is in the resolv.conf file with IP 127.0.0.53
in the erlier version there was an additional entry on top with the IP of the
local DNS server(router).
when i nfsboot ubuntu 18.04, adjust the /etc/resolv.conf file by hand to get
internet address resolving to work,
when i then install ubuntu 18.04 from that environment to the local
harddrive, the networksettings on the newly installed local harddisk is always
setted up to "manual" IP in the /etc/network/interfaces - so it will not get a
proper IP from the router.
after a new installation, i always have to set it up "dhcp" to get the IP
from the router as usual.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765765/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
