xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
Bug #1621393 reported by
Marius Gedminas
This bug affects 21 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
Undecided
|
Unassigned | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Unassigned |
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
description: | updated |
tags: | added: regression-update |
description: | updated |
Changed in livecd-rootfs (Ubuntu): | |
importance: | Undecided → High |
Changed in cloud-images: | |
status: | New → Fix Released |
To post a comment you must log in.
Also /etc/resolv.conf doesn't have a root write permission which is probably the root cause of this problem