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

[GGeorg]

Hi,

in the meanwhile you can use this Workaround in Vagrantfile
(multimachine example):

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
     servers.each do |machine|
          config.vm.define machine["hostname"] do |node|
               node.vm.provision "shell", inline: "ln -nsf ../run/resolvconf/resolv.conf /etc/resolv.conf", privileged: true, name: "FIX RESOLV.CONF"
          end
     end
end

-- 
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:
  Confirmed

Bug description:
  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