[Bug 1713149] Re: resolv.conf symlink is broken after clean debootstrap

[Launchpad Bug Tracker]

This bug was fixed in the package resolvconf - 1.79ubuntu8

---------------
resolvconf (1.79ubuntu8) artful; urgency=medium

  * Dereference /etc/resolf.conf when creating runtime configuration when
    migrating to resolvconf managed /etc/resolv.conf. The contents of
    /etc/resolv.conf (rather than the symlink target information) is
    needed in /run/resolvconf/resolv.conf and
    /run/resolvconf/interface/original.resolvconf during migration until
    resolvconf updates the config next. LP: #1713149

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Tue, 29 Aug 2017 14:04:33
+0100

** Changed in: resolvconf (Ubuntu)
       Status: New => Fix Released

-- 
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/1713149

Title:
  resolv.conf symlink is broken after clean debootstrap

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Reproducer:
   - debootstrap artful artful

  Expected:
   - "chroot artful cat /etc/resolv.conf" doesn't fail.
   - /etc/resolv.conf is a symlink to something valid in /run

  Actual:
   - "chroot artful cat /etc/resolv.conf" gets you "No such file or directory"
   - /etc/resolv.conf is a symlink to "../run/resolvconf/resolv.conf"
   - "../run/resolvconf/resolv.conf" is a symlink to "../run/systemd/resolve/stub-resolv.conf" which is an invalid symlink as that points to /run/run/systemd/resolve/stub-resolv.conf" rather than "/run/systemd/resolve/stub-resolv.conf"

  This causes all LXC image creation to fail, causing autopkgtest to
  fail (as noticed by the kernel team) and has been causing all images
  to fail building on the upstream build system for the past two days.


  root at vm04:~# chroot artful ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 4.0K
  -rw-r--r-- 1 root root    0 Aug 25 20:21 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  lrwxrwxrwx 1 root root   39 Aug 25 20:18 resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

  root at vm04:~# chroot zesty ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 8.0K
  -rw-r--r-- 1 root root    0 Aug 25 20:20 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  -rw-r--r-- 1 root root  357 Aug 25 20:15 resolv.conf

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