[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf

[Thomas]

So I just tested again with the released image on Vagrant Atlas
(https://atlas.hashicorp.com/ubuntu/boxes/xenial64/versions/20160914.0.0)
and the image from Ubuntu Cloud Images (https://cloud-
images.ubuntu.com/xenial/current/xenial-server-cloudimg-
amd64-vagrant.box) and the bug still remains. So the `/etc/resolv.conf`
file is empty and no hosts can be resolved and thus not reached.

-- 
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/1621393

Title:
  xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf

Status in cloud-images:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released

Bug description:
  [SRU Justification]
  This is a regression introduced in the previous SRU of livecd-rootfs.

  [Test case]
  1. vagrant init ubuntu/xenial64
  2. vagrant up
  3. vagrant ssh
  4. ping google.com

  Expected result:
  - ping succeeds

  Actual result:
  - name resolution fails

  Inspecting closely reveals that this image has a 0-length
  /etc/resolv.conf.  Replacing it with a symlink to
  /run/resolvconf/resolv.conf fixes things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1621393/+subscriptions