Changed the disk from virtio to IDE without change. Added debug to the kernel options and got a bit more info in journal but it looks odd. There is a dhclient with PID 496 early on. Which does not seem to exit. But then later on there is a 699 getting killed which matches the pid file but never seems to be started.
Could be a gap from pivoting root but I cannot really say how to tell for sure. ** Attachment added: "Output of journalctl after adding debug to kernel options" https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1466790/+attachment/4422288/+files/journal.txt -- 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: New 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
