[Bug 1801134] Re: /etc/resolv.conf broken in Xenial minimal

[Brian Murray]

Hello Cody, or anyone else affected,

Accepted livecd-rootfs into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.408.41 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: livecd-rootfs (Ubuntu Xenial)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1801134

Title:
  /etc/resolv.conf broken in Xenial minimal

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Committed

Bug description:
  DNS was broken in Xenial minimal images under some circumstances due
  to a 0-byte /etc/resolv.conf file.

  [Test Case]
  Build Xenial Minimal Image
  Check /etc/resolv.conf and confirm it is a symlink and not a 0-byte file.

  [Regression Potential]
  Regression would manifest in inability to do name resolution completely.

  Although a 0-byte /etc/resolv.conf does currently prevent name
  resolution, it can be repaired by running `# dhclient`.

  An example of a regression would potentially be that the above
  workaround is no longer effective.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1801134/+subscriptions