apparmor get_cgroup fails when creating lxc with juju local provider

[Sean Feole]

I wanted to try out 1.18 on the local provider for armhf.

juju-core:
  Installed: 1.18.0-0ubuntu1
  Candidate: 1.18.0-0ubuntu1

After installing juju-local, followed by juju init. The local bootstrap appears to start successfully. When deploying charms the following error occurs below. This also occurs when adding a machine by itself with the ' $juju add-machine ' command.

ubuntu@g7:/var/log/juju-ubuntu-local$ juju status
environment: local
machines:
  "0":
    agent-state: started
    agent-version: 1.18.0.1
    dns-name: localhost
    instance-id: localhost
    series: trusty
  "1":
    agent-state-info: '(error: error executing "lxc-start": command get_cgroup failed
      to receive response)'
    instance-id: pending
    series: precise
services: {}

[Dave Cheney (dave-cheney)]

I believe this is caused by https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1304167

[Dave Cheney (dave-cheney)]

A workaround is

sudo apt-get remove apparmor -y #removes lxc
sudo apt-get install lxc -y

[Curtis Hovey (sinzui)]

I am keeping the juju-core aspect tied to this bug (Triage) so that I can easilly track the issue in regards to ubuntu to. There are no code changes to made to juju-core.

[Dave Cheney (dave-cheney)]

Look in dmesg, it'll tell you what is failing.

On Fri, Apr 11, 2014 at 2:03 PM, Curtis Hovey <email address hidden> wrote:
> ** Changed in: juju-core
> Milestone: None => 1.19.0
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1305280
>
> Title:
> juju command get_cgroup fails when creating new machines, local
> provider arm32
>
> Status in juju-core:
> Triaged
> Status in "apparmor" package in Ubuntu:
> New
>
> Bug description:
> I wanted to try out 1.18 on the local provider for armhf.
>
> juju-core:
> Installed: 1.18.0-0ubuntu1
> Candidate: 1.18.0-0ubuntu1
>
> After installing juju-local, followed by juju init. The local
> bootstrap appears to start successfully. When deploying charms the
> following error occurs below. This also occurs when adding a machine
> by itself with the ' $juju add-machine ' command.
>
> ubuntu@g7:/var/log/juju-ubuntu-local$ juju status
> environment: local
> machines:
> "0":
> agent-state: started
> agent-version: 1.18.0.1
> dns-name: localhost
> instance-id: localhost
> series: trusty
> "1":
> agent-state-info: '(error: error executing "lxc-start": command get_cgroup failed
> to receive response)'
> instance-id: pending
> series: precise
> services: {}
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1305280/+subscriptions

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jamie Strandboge (jdstrand)]

There were several policy bugs fixed in lxc that might fix this. Is this still a problem on 14.10? If so, can you post the apparmor denials from /var/log/syslog on the host and in the container?

[Launchpad Janitor (janitor)]

[Expired for apparmor (Ubuntu) because there has been no activity for 60 days.]