Seems on Vivid this was fixed in some way (at least systemd was very outdated in the VM I had quickly booted up). Before the update systemd was at version 219-4*, now updated to 219-7ubuntu3. The wily VM was up-to-date and runs systemd 220-7ubuntu1. Could it be that something about keeping daemons started during ifup running be accidentally dropped?
** Summary changed: - dhclient not started on boot + dhclient does not remain running on boot ** Description changed: 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. + 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466790 Title: dhclient does not remain running on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1466790/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
