Azure: /etc/resolv.conf points to /run/resolvconf/resolv.conf in artful

Bug #1722663 reported by Scott Moser
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloud-images
Fix Released
Critical
Unassigned

Bug Description

$ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Oct 6 12:00 /etc/resolv.conf -> ../run/resolvconf/resolv.conf

$ cat /etc/cloud/build.info
build_name: server
serial: 20171005.1

$ lsb_release -sc
artful
$ for p in resolvconf nplan; do dpkg-query --show $p; done
resolvconf
nplan 0.29

So what we see is the symlink points as if resolvconf was installed
and managing /etc/resolv.conf, but it is not and should not be.

Note, that /run/systemd/resolve/resolv.conf is correct, just not used.

$ grep '^[^#]' /run/systemd/resolve/resolv.conf
nameserver 168.63.129.16
search ng102m4hnhaedfnxz3boonlkbb.xx.internal.cloudapp.net

Related branches

Scott Moser (smoser)
Changed in cloud-images:
status: New → Confirmed
summary: - /etc/resolv.conf points to /run/resolvconf/resolv.conf in artful
+ Azure: /etc/resolv.conf points to /run/resolvconf/resolv.conf in artful
Scott Moser (smoser)
description: updated
Changed in cloud-images:
importance: Undecided → Critical
Revision history for this message
Scott Moser (smoser) wrote :

Just for reference really, bug 1722668 in cloud-init means that we have
some more work to do still, but that only affects "publishing" of the
hostname it is very much non-fatal.

Revision history for this message
Scott Moser (smoser) wrote :

$ cat /etc/cloud/build.info
build_name: server
serial: 20171011

$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53

search phnsbsibnbxenpp2lbuyobkrpb.bx.internal.cloudapp.net

Changed in cloud-images:
status: Confirmed → Fix Committed
status: Fix Committed → Fix Released
Revision history for this message
Scott Moser (smoser) wrote :

I've marked fix-released, if you disagree (since only fixed in a daily), then set back.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.