hm however, i would have expected the netboot these days to work
without ifupdown, and be netplan driven and have the right configs
throughtout.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I confirmed that the /etc/resolv.conf and network-manager can work by
removing the two lines of /etc/network/interfaces:
auto eth0
iface eth0 inet manual
The /etc/resolv.conf will be re-synced by NM although it seems to be
managed by systemd-resolved.
--
You received this bug notification
I confirm this issue still exists when doing a PXE netboot of Ubuntu
16.04 Desktop and also with a PXE netboot of an Ubuntu 18.04 LTS (Bionic
Beaver) Desktop Daily Build.
I also use the workaround to comment out the all the interfaces in
/etc/network/interfaces except the loopback adapter and the
Moving bug to ubiquity as that's where we should be checking for that
kind of scenario and fallback to copying /rofs/etc/network/interfaces if
the interface is marked as manual (static should still be copied).
** No longer affects: ubiquity
** Package changed: casper (Ubuntu) = ubiquity (Ubuntu)
Relevant earlier report: bug #946215:
Tracked it down to 23networking in casper writting
/etc/resolv.conf in the target which obviously won't
quite work because of resolvconf.
I'll do some copy/pasting of the code I wrote for LTSP in a similar use case.
--
You received this bug
Mathieu wrote:
Would it be sufficient to just skip adding the manual method interfaces to
/etc/network/interfaces
I am guessing that the interface was once defined as inet manual in
order to prevent both ifup and NM from messing with it.
Omitting the stanza entirely will prevent ifup from
** Summary changed:
- netboot insall of live cd results in a manual network interface configuration
+ netboot install of live CD results in unconfigured network interface
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
