[Bug 931220] Re: lxc.conf upstart job fails to spawn containers at boot time

[Serge Hallyn]

Note that I still can't reproduce this here.

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

Title:
  lxc.conf upstart job fails to spawn containers at boot time

Status in “lxc” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  root at vorash:~# cat /var/log/upstart/lxc.log 
  + [ -f /etc/default/lxc ]
  + . /etc/default/lxc
  + LXC_AUTO=true
  + USE_LXC_BRIDGE=false
  + LXC_BRIDGE=lxcbr0
  + LXC_ADDR=10.0.3.1
  + LXC_NETMASK=255.255.255.0
  + LXC_NETWORK=10.0.3.0/24
  + LXC_DHCP_RANGE=10.0.3.2,10.0.3.254
  + LXC_DHCP_MAX=253
  + [ xtrue = xtrue ]
  + ls /etc/lxc/auto/v6test01.conf
  + basename /etc/lxc/auto/v6test01.conf .conf
  + c=v6test01
  + lxc-info -n v6test01
  + grep state
  + grep -q RUNNING
  + lxc-start -l debug -o /run/debug -n v6test01 -f /etc/lxc/auto/v6test01.conf -d

  root at vorash:~# cat /run/debug 
        lxc-start 1329097397.477 ERROR    lxc_start - inherited fd 21 on socket:[17416]

  
  The first listing is the output of lxc.conf running with "set -x" and upstart logging with an added "-l debug -o /run/debug" to the lxc-start command line.
  The second is the output in /run/debug

  Apparently lxc-start is inheriting an fd from upstart causing lxc to
  fail to start.

  I'm marking this high against lxc and also adding an upstart task in
  case we're inheriting this fd from some upstart issue.

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