i never used ip=dhcp in the boot menu entries.
strange i had those resolv issue with ubuntu 19.04 daily (pending) from
2019-02-14 for sure.
now i tried again with ubuntu 19.04 daily (pending) from 2019-02-20, and now it
seems to be not an issue.
i also tried the other versions 18.10 and 18.04.2... there it is no
issue with resolv anymore.
the only thing i could notice now was, that resolving (ping google.de)
takes a bit longer under 19.04 daily than under 18.10 / 18.04.2... or
maybe it is only my mind.
at the moment i can not reproduce my ony reported resolv issue. :/
pxe boot menu entries:
########################################
LABEL ubuntu-daily-x64
MENU LABEL Ubuntu x64 Daily-Live
KERNEL http://192.168.0.1/nfs/ubuntu-daily-x64/casper/vmlinuz
INITRD http://192.168.0.1/nfs/ubuntu-daily-x64/casper/initrd
APPEND nfsroot=192.168.0.1:/srv/nfs/ubuntu-daily-x64 ro netboot=nfs
file=/cdrom/preseed/ubuntu.seed boot=casper -- debian-installer/language=de
console-setup/layoutcode=de keyboard-configuration/layoutcode=de
keyboard-configuration/variant=German
TEXT HELP
Boot to Ubuntu x64 Daily-Live
User: ubuntu
ENDTEXT
########################################
LABEL ubuntu-x64
MENU LABEL Ubuntu x64
KERNEL http://192.168.0.1/nfs/ubuntu-x64/casper/vmlinuz
INITRD http://192.168.0.1/nfs/ubuntu-x64/casper/initrd
APPEND nfsroot=192.168.0.1:/srv/nfs/ubuntu-x64 ro netboot=nfs
file=/cdrom/preseed/ubuntu.seed boot=casper systemd.mask=tmp.mount --
debian-installer/language=de console-setup/layoutcode=de
keyboard-configuration/layoutcode=de keyboard-configuration/variant=German
TEXT HELP
Boot to Ubuntu x64 Live
User: ubuntu
ENDTEXT
########################################
LABEL ubuntu-lts-x64
MENU LABEL Ubuntu LTS x64
KERNEL http://192.168.0.1/nfs/ubuntu-lts-x64/casper/vmlinuz
INITRD http://192.168.0.1/nfs/ubuntu-lts-x64/casper/initrd
APPEND nfsroot=192.168.0.1:/srv/nfs/ubuntu-lts-x64 ro netboot=nfs
file=/cdrom/preseed/ubuntu.seed boot=casper systemd.mask=tmp.mount --
debian-installer/language=de console-setup/layoutcode=de
keyboard-configuration/layoutcode=de keyboard-configuration/variant=German
TEXT HELP
Boot to Ubuntu LTS x64 Live
User: ubuntu
ENDTEXT
--
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 : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
