/etc/resolv.conf is not a symlink to /run/resolvconf/resolv.conf for xenial/20160907.1.0 box
Bug #1621469 reported by
Rudolph P
This bug report is a duplicate of:
Bug #1621393: xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf.
Edit
Remove
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-images |
New
|
Undecided
|
Unassigned | ||
Bug Description
Running latest xenial64 box (specifically 20160907.1.0) through vagrant, resolver configuration seems broken. /etc/resolv.conf has zero-size and is not a symlink to configuration in /run/resolvconf, meaning that all DNS resolution fails. This is also logged in syslog. All other network configuration seems fine - once the symlink is fixed box is able to resolve normally.
I have attached a log showing an attempt at bringing up a vagrant box that has the issue, and resolving it by fixing the symlink
Revision history for this message
| Rudolph P (roprop) wrote | #1 |
To post a comment you must log in.
