touch-packages team mailing list archive

[Tim Van Steenburgh <tvansteenburgh@xxxxxxxxx>]

I don't have an easy way to repro, all this occurs fairly regularly on
our jenkins slave.

Ubuntu 14.04 LTS (GNU/Linux 3.13.0-29-generic x86_64)

juju version: 1.20.13-trusty-amd64

1 ppa installed: http://ppa.launchpad.net/juju/stable/ubuntu

$ dpkg -l | egrep -e "(lxc|apparmor|cgmanager)"
ii  apparmor                             2.8.95~2430-0ubuntu5                amd64        User-space parser utility for AppArmor
ii  cgmanager                            0.24-0ubuntu7                       amd64        Central cgroup manager daemon
ii  dh-apparmor                          2.8.95~2430-0ubuntu5.1              all          AppArmor debhelper routines
ii  libapparmor-perl                     2.8.95~2430-0ubuntu5                amd64        AppArmor library Perl bindings
ii  libapparmor1:amd64                   2.8.95~2430-0ubuntu5                amd64        changehat AppArmor library
ii  libcgmanager0:amd64                  0.24-0ubuntu6                       amd64        Central cgroup manager daemon (client library)
ii  liblxc1                              1.0.3-0ubuntu3                      amd64        Linux Containers userspace tools (library)
ii  lxc                                  1.0.3-0ubuntu3                      amd64        Linux Containers userspace tools
ii  lxc-templates                        1.0.3-0ubuntu3                      amd64        Linux Containers userspace tools (templates)
ii  python3-lxc                          1.0.3-0ubuntu3                      amd64        Linux Containers userspace tools (Python 3.x bindings)

$ ps -ef | egrep -e "(cgproxy|cgmanager)"
root       348     1  0 Nov03 ?        00:07:44 /sbin/cgmanager --sigstop -m name=systemd
jenkins  10661  9679  0 18:36 pts/14   00:00:00 egrep -e (cgproxy|cgmanager)

There are many containers on this host and I'm not sure which one(s) are
being used, but regardless of which I pick I get the same result:

jenkins@charm-bundle-slave:/var/lib/juju/containers$ sudo lxc-start -P /var/lib/juju/containers -n juju-trusty-lxc-template -L -l trace -o outout                                                                                                                                    
lxc-start: Permission denied - Failed to make / rslave
lxc-start: failed to setup rootfs for 'juju-trusty-lxc-template'
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'juju-trusty-lxc-template'

Advice?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1402005

Title:
  agent-state-info: 'error executing "lxc-start": command get_cgroup
  failed to receive response'

Status in juju-core:
  New
Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  We are seeing a few deploys in our automated charm testing fail due to
  not being able to execute lxc-start.

  The error we are seeing is:
    "1":
      agent-state-info: 'error executing "lxc-start": command get_cgroup failed to receive
        response'
      instance-id: pending
      series: precise
  ref: http://reports.vapour.ws/charm-tests/charm-bundle-test-10698-results/charm/charm-testing-lxc/2

  Tim V. has done some initial research on it:
  https://github.com/lxc/lxc/issues/189
  which lead to  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1296459
  The fix there was to have 2.8.95~2430-0ubuntu3 installed. Our charm testing infrastructure is running 2.8.95~2430-0ubuntu5.

  Any help on determining why lxc-start is failing here would be much
  appreciated.

  -thanks,
  Antonio

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