[Bug 880020] Re: oneiric container install problem: resolvconf

Launchpad Bug Tracker 880020 at bugs.launchpad.net
Mon Nov 14 05:54:32 UTC 2011


This bug was fixed in the package lxc - 0.7.5-0ubuntu8.2

---------------
lxc (0.7.5-0ubuntu8.2) oneiric-proposed; urgency=low

  * debian/patches/0009-ubuntu-template-drop-resolvconf.patch:
    Drop resolvconf from package list for oneiric containers.  It appears
    to stop containers from getting a useful resolv.conf without doing
    ifdown; ifup; and is apparently unwanted anyway. (LP: #880020)
  * debian/lxcguest.lxcguest.upstart: mkdir /run/lock on boot
    (LP: #880030)
  * debian/fstab.lxc and debian/fstab.libvirt: mount tmpfs on /run/lock,
    not /var/lock (as per new stock /lib/init/fstab).
 -- Serge Hallyn <serge.hallyn at ubuntu.com>   Wed, 02 Nov 2011 22:49:42 +0000

** Changed in: lxc (Ubuntu Oneiric)
       Status: Fix Committed => Fix Released

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

Title:
  oneiric container install problem: resolvconf

Status in “debootstrap” package in Ubuntu:
  Invalid
Status in “lxc” package in Ubuntu:
  Fix Released
Status in “debootstrap” source package in Oneiric:
  Confirmed
Status in “lxc” source package in Oneiric:
  Fix Released

Bug description:
  host: oneiric with server minimal install + lxc + bridge_utils (bridge manually set up)
  guest: oneiric

  no value in resolv.conf:
  root at orig:~# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

  removing resolvconf installation from lxc-ubuntu fix it

  =============================================
  SRU Justification:
  1. Impact: Newly created containers are unable to use the network.
  2. Development fix: remove resolvconf from the list of packages to install when creating an oneiric container.
  3. Stable fix: same as development fix.
  4. Test case: create a container, start it, try to access the network.
  5. Regression potential: we only stop installing resolvconf by default, which is not a package we want by default anyway.
  =============================================

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




More information about the foundations-bugs mailing list