touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

> Could it be that something about keeping daemons started during ifup
running be accidentally dropped?

Not that I know of, and in my wily VMs dhclient runs happily.

I don't know whether ifupdown has some useful debugging facilities. I
tried adding /usr/bin/strace -fvvs1024 -o /run/ifup.trace to
/etc/init.d/networking, but it doesn't give much information (in
particular, it doesn't end up calling dhclient). Do you get anything
useful if you set VERBOSE=yes in /etc/default/networking and reboot?
(Please attach journal again)

** Package changed: ubuntu => ifupdown (Ubuntu)

** Changed in: ifupdown (Ubuntu)
       Status: Confirmed => Incomplete

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

Title:
  dhclient does not remain running on boot

Status in ifupdown package in Ubuntu:
  Incomplete

Bug description:
  Not sure whether this is a systemd or ifupdown issue. I just happened to notice today for a Wily VM (set up from server iso) that I failed to get a DNS resolution for a VM I started earlier the day. DNS updates in my case are related to DHCP updates. And on the DHCP/DNS server I noticed that the IP address had been removed at some point. Looking at the VM, I find no dhclient being started. When I manually run ifdown and ifup on the interface this does happen. But not whenever I boot.
  Curious about this I also checked a Vivid VM (also server install) and this looks the same. However for Vivid this seems fixed in the latest versions.

  Network config in /etc/network/interfaces:
  auto eth0
  iface eth0 inet dhcp

  Expected result:
  dhclient running for eth0

  Actual result after boot:
  No dhclient process is running.

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