touch-packages team mailing list archive

[Jamie Strandboge <jamie@xxxxxxxxxx>]

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?

** Changed in: apparmor (Ubuntu)
       Status: Confirmed => Incomplete

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

Title:
  apparmor get_cgroup fails when creating lxc with juju local provider

Status in juju-core:
  Invalid
Status in “apparmor” package in Ubuntu:
  Incomplete

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