[Bug 1000244] Re: Symlink /etc/resolv.conf does not exist after installation or upgrade of resolvconf -- various causes

[Thomas Hood]

> resolvconf/linkify-resolvconf: false

This is always the case after installation because the Ubuntu resolvconf
postinst does the following.

    db_set resolvconf/linkify-resolvconf false

This is done for a good reason: it is done in order to prevent the
postinst from attempting to linkify again on upgrade. Thus the admin can
remove the symlink /etc/resolv.conf if she wants to and even though she
doesn't bother to change the answer to resolvconf/linkify-resolvconf,
the symlink won't be recreated on package upgrade.

As I wrote in #1085849, however, I'd like to see another mechanism used
to achieve the same end, so that we can tell what the original answer to
resolvconf/linkify-resolvconf was in cases like this where the symlink
is mysteriously missing after installation. In Debian I have just
implemented this feature another way. The Debian postinst doesn't change
resolvconf/linkify-resolvconf; instead it creates a flag file and
refrains from linkifying again if the flag file is present. I hope that
Ubuntu adopts this mechanism too when 1.71 is merged.

Anyway, Vince, despite the foregoing, can you shed any light on why the
symlink /etc/resolv.conf might have been missing from your system after
upgrade? Which distro and flavor did you install originally? Is it
virtual hardware? Any unusual images used? Any unusual preseeding done?
Any unusual VPN client or similar installed?

(You probably already know that you can recreate the symlink by running
"sudo dpkg-reconfigure resolvconf".)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1000244

Title:
  Symlink /etc/resolv.conf does not exist after installation or upgrade
  of resolvconf -- various causes

Status in “resolvconf” package in Ubuntu:
  Confirmed

Bug description:
  I upgraded an 11.10 install to 12.04, and now I'm unable to resolve
  domain names because Network Manager does not populate my
  /etc/resolv.conf file.

  For example, my local wireless router uses the domain "mylocaldomain"
  and nameservers 10.157.10.12 and 10.157.10.14, so in 11.10, after
  connecting to the router I would see this in my /etc/resolv.conf:

  domain mylocaldomain
  search mylocaldomain
  nameserver 10.157.10.12
  nameserver 10.157.10.14

  Now /etc/resolv.conf contains the settings last set before I upgraded
  to 12.04, and doesn't update them for whatever network I'm currently
  on. I have to manually guess the settings and modify /etc/resolv.conf
  in order to resolve domain names.

  I believe this may be related to
  https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/922677 and
  how the "resolvconf" program has been introduce to manage this. I
  believe this is a new bug with how prior installs are improperly
  upgraded.

  I tried removing the line "dns=dnsmasq" from
  /etc/NetworkManager/NetworkManager.conf and then running `sudo restart
  network-manager`, but that had no effect.

  I tried running `resolvconf --enable-updates` but I get the error
  "resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing
  anything."

  Based on https://help.ubuntu.com/12.04/serverguide/network-
  configuration.html#name-resolution, I tried establishing this symlink
  myself, but the file /run/resolvconf/resolv.conf does not exist on my
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
  Date: Wed May 16 09:57:25 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012)
  IpRoute:
   default via 192.168.1.1 dev eth2  proto static 
   169.254.0.0/16 dev eth2  scope link  metric 1000 
   192.168.1.0/24 dev eth2  proto kernel  scope link  src 192.168.1.205  metric 2 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-05-10 (5 days ago)
  nmcli-dev:
   DEVICE     TYPE              STATE         DBUS-PATH                                  
   eth2       802-11-wireless   connected     /org/freedesktop/NetworkManager/Devices/1  
   eth0       802-3-ethernet    unavailable   /org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING         VERSION    STATE           NET-ENABLED   WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
   running         0.9.4.0    connected       enabled       enabled         enabled    enabled         enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions