[Bug 1621393] Re: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
Launchpad Bug Tracker
1621393 at bugs.launchpad.net
Sat Sep 10 00:20:11 UTC 2016
This bug was fixed in the package livecd-rootfs - 2.430
---------------
livecd-rootfs (2.430) yakkety; urgency=medium
[ Michael Vogt ]
* live-build/ubuntu-core/hooks/01-setup_user.chroot:
- do not create "ubuntu" user for ubuntu-core anymore, the
console-conf package will create this user now
* live-build/ubuntu-core/hooks/02-add_user_to_groups.chroot
- dropped
[ Steve Langasek ]
* live-build/ubuntu-cpc/hooks/042-vagrant.binary: fix unmount handling
so that the teardown is done properly /before/ we try to make an
image from our filesystem, since otherwise /etc/resolv.conf is broken.
LP: #1621393.
-- Steve Langasek <steve.langasek at ubuntu.com> Fri, 09 Sep 2016
15:57:27 -0700
** Changed in: livecd-rootfs (Ubuntu)
Status: Confirmed => Fix Released
--
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
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
More information about the foundations-bugs
mailing list