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

[Serge Hallyn]

** Description changed:

  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.
+ =============================================

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

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