[Bug 1271941] [NEW] lxc container creation fails on trusty host service units

[James Page]

Public bug reported:

environment: trusty
machines:
  "0":
    agent-state: started
    agent-version: 1.16.5
    dns-name: test-05.os.magners.qa.lexington
    instance-id: /MAAS/api/1.0/nodes/node-1fece8ca-b844-11e2-91a5-d4bed9a84493/
    series: trusty
    containers:
      0/lxc/0:
        agent-state-info: '(error: symlink /var/lib/lxc/juju-machine-0-lxc-0/config
          /etc/lxc/auto/juju-machine-0-lxc-0.conf: no such file or directory)'
        instance-id: pending
        series: trusty
      0/lxc/1:
        agent-state-info: '(error: symlink /var/lib/lxc/juju-machine-0-lxc-1/config
          /etc/lxc/auto/juju-machine-0-lxc-1.conf: no such file or directory)'
        instance-id: pending
        series: trusty
      0/lxc/2:
        agent-state-info: '(error: symlink /var/lib/lxc/juju-machine-0-lxc-2/config
          /etc/lxc/auto/juju-machine-0-lxc-2.conf: no such file or directory)'
        instance-id: pending
        series: trusty
      0/lxc/3:
        agent-state-info: '(error: symlink /var/lib/lxc/juju-machine-0-lxc-3/config
          /etc/lxc/auto/juju-machine-0-lxc-3.conf: no such file or directory)'
        instance-id: pending
        series: trusty
      0/lxc/4:
        agent-state-info: '(error: symlink /var/lib/lxc/juju-machine-0-lxc-4/config
          /etc/lxc/auto/juju-machine-0-lxc-4.conf: no such file or directory)'
        instance-id: pending
        series: trusty
      0/lxc/5:
        agent-state-info: '(error: symlink /var/lib/lxc/juju-machine-0-lxc-5/config
          /etc/lxc/auto/juju-machine-0-lxc-5.conf: no such file or directory)'
        instance-id: pending
        series: trusty

I think that autostart configuration has changed - reading from lxc-
autostart:

DESCRIPTION
       lxc-autostart  processes containers with lxc.start.auto set. It lets the user start, shutdown, kill, restart containers in the right order, wait‐
       ing the right time. Supports filtering by lxc.group or just run against all defined containers. It can also be used by  external  tools  in  list
       mode where no action will be performed and the list of affected containers (and if relevant, delays) will be shown.

so instead of creating symlinks, the lxc.start.auto configuration should
be set.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: juju-core 1.17.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Thu Jan 23 13:49:09 2014
Dependencies:
 gcc-4.8-base 4.8.2-14ubuntu2
 libc6 2.18-0ubuntu6
 libgcc1 1:4.8.2-14ubuntu2
 libgo4 4.8.2-14ubuntu2
 multiarch-support 2.18-0ubuntu6
ProcEnviron:
 TERM=screen-bce
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: juju-core
     Importance: Undecided
         Status: New

** Affects: juju-core (Ubuntu)
     Importance: Critical
         Status: Triaged


** Tags: amd64 apport-bug trusty uec-images

** Also affects: juju-core
   Importance: Undecided
       Status: New

** Changed in: juju-core (Ubuntu)
       Status: New => Triaged

** Changed in: juju-core (Ubuntu)
   Importance: Undecided => Critical

** Changed in: juju-core (Ubuntu)
    Milestone: None => ubuntu-14.04-feature-freeze

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1271941

Title:
  lxc container creation fails on trusty host service units

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions