touch-packages team mailing list archive

[Phil Lello <phil@xxxxxxxxxxxxxxx>]

Yes, resolvconf is installed, and calls the supplied script - which I
now notice needs the banner comment correcting - I'll provide an updated
script as an attachment.

The key to understanding this issue is that it's a diskless machine
booting via DHCP and using NFS to provide a root partition from a remote
server.

In this configuration, the network interface is configured early in boot
by the initramfs image, not the main boot process, so resolvconf isn't
yet present. Once the root filesystem (containing amongst other things,
resolvconf) is mounted, the network interface is left alone, rather than
re-configuring. With a network-mounted root filesystem, correct
behaviour is to leave the network interface set to manual, since re-
configuration would break the root mount.

Since the network scripts don't reconfigure the network interface, the
resolvconf hook in /etc/network/if-up.d/000resolvconf doesn't get
called.

The proposed solution to this issue is to use the settings already
received over DHCP in the initramfs environment, since these are present
in the file(s) /run/net-<iface>.conf.

** Attachment added: "netboot"
   https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1473727/+attachment/4428386/+files/netboot

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1473727

Title:
  No DNS servers after netboot

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 14.04 / resolvconf 1.69ubuntu1.1

  When netbooting a xen VM, I see the following output:

   address: 192.168.1.180    broadcast: 192.168.1.255    netmask:
  255.255.255.0

   gateway: 192.168.1.1      dns0     : 192.168.1.1      dns1   :
  0.0.0.0

  So I know DHCP is working.

  However, resolv.conf doesn't get updated - the interface is set to
  manual as DHCP was handled at the initrd level.

  Please let me know how I can help get this fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1473727/+subscriptions