Ubuntu
juju-core package

LXC permission denied issue with 1.17.7

Bug #1299588 reported by Nicolas Thomas
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Ian Booth
juju-core 1.19.0
1.18
Fix Released
Critical
Ian Booth
juju-core 1.18.0
juju-core (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Was doing deployment of OpenStack using some lxc on MAAS.

Working well with 1.16.6 upgrading to 1.17.7 deployment seems stuck .. only for lxc contained one.

A lot of the following :

machine-11: 2014-03-29 18:50:16 ERROR juju runner.go:220 worker: exited
"lxc-provisioner": permission denied

from juju debug-log..

Might be easy to reproduce

Related branches

lp:~wallyworld/juju-core/container-provisioner-retrywatcher
Juju Engineering: Pending requested
Diff: 151 lines (+44/-3)
5 files modified
worker/provisioner/export_test.go (+5/-0)
worker/provisioner/kvm-broker_test.go (+10/-0)
worker/provisioner/lxc-broker_test.go (+10/-0)
worker/provisioner/provisioner.go (+12/-2)
worker/provisioner/provisioner_task.go (+7/-1)
lp:~wallyworld/juju-core/container-provisioner-retrywatche-1.18
Juju Engineering: Pending requested
Diff: 151 lines (+44/-3)
5 files modified
worker/provisioner/export_test.go (+5/-0)
worker/provisioner/kvm-broker_test.go (+10/-0)
worker/provisioner/lxc-broker_test.go (+10/-0)
worker/provisioner/provisioner.go (+12/-2)
worker/provisioner/provisioner_task.go (+7/-1)
lp:ubuntu/trusty-proposed/juju-core
lp:~smoser/ubuntu/precise/juju-core/cloud-tools
lp:~ubuntu-cloud-archive/ubuntu/precise/juju-core/precise-ctools
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in juju-core (Ubuntu):
status: New → Confirmed
Darryl Weaver (dweaver)
tags: added: micro-cluster
David Britton (dpb)
tags: added: landscape
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

It's happening for me too. I used the manual provider + kapil's digital ocean plugin. I deployed ubuntu to a new machine, and then another service to lxc on that machine. machine log is attached, this is the last part:

2014-04-01 22:39:27 INFO juju.utils.apt apt.go:126 Running: [apt-get --option=Dpkg::Options::=--force-confold --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install --target-release precise-updates/cloud-tools lxc]
2014-04-01 22:39:49 INFO juju runner.go:262 worker: start "lxc-provisioner"
2014-04-01 22:39:49 ERROR juju runner.go:220 worker: exited "lxc-provisioner": permission denied
2014-04-01 22:39:49 INFO juju runner.go:254 worker: restarting "lxc-provisioner" in 3s
2014-04-01 22:39:52 INFO juju runner.go:262 worker: start "lxc-provisioner"
2014-04-01 22:39:52 ERROR juju runner.go:220 worker: exited "lxc-provisioner": permission denied
2014-04-01 22:39:52 INFO juju runner.go:254 worker: restarting "lxc-provisioner" in 3s

And then it just loops.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Same thing happened on AWS. Steps to reproduce:

juju bootstrap
juju deploy ubuntu
juju deploy ubuntu --to lxc:1

juju ssh 1
tail -f /var/log/juju/machine-1.log

You'll see:
(...)
2014-04-01 23:22:36 DEBUG juju.worker.logger logger.go:60 logger setup
2014-04-01 23:22:36 DEBUG juju.worker.machineenvironment machineenvironmentworker.go:70 write system files: true
2014-04-01 23:22:36 DEBUG juju.worker.rsyslog worker.go:76 starting rsyslog worker mode 1 for "machine-1" ""
2014-04-01 23:22:36 INFO juju runner.go:262 worker: start "authenticationworker"
2014-04-01 23:22:36 INFO juju.worker.machiner machiner.go:88 setting addresses for machine-1 to ["10.252.117.118" "fe80::2000:aff:fefc:7576"]
2014-04-01 23:22:36 DEBUG juju.worker.logger logger.go:45 reconfiguring logging from "<root>=DEBUG" to "<root>=WARNING;unit=DEBUG"
2014-04-01 23:22:36 WARNING juju.cmd.jujud machine.go:277 determining kvm support: exit status 1
no kvm containers possible
2014-04-01 23:30:48 ERROR juju runner.go:220 worker: exited "lxc-provisioner": permission denied
2014-04-01 23:30:51 ERROR juju runner.go:220 worker: exited "lxc-provisioner": permission denied

And no container is created, nor started.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Deploying a containerized service to the bootstrap node works, i.e.:

juju deploy ubuntu --to lxc:0

Revision history for this message
David Britton (dpb) wrote :

Seems like it's very easy to repro on AWS. Anything but the bootstrap node gets this when you deploy lxc ala:

juju deploy --to lxc:1 ubuntu

Ian Booth (wallyworld)
Changed in juju-core (Ubuntu):
assignee: nobody → Ian Booth (wallyworld)
assignee: Ian Booth (wallyworld) → nobody
Changed in juju-core:
assignee: nobody → Ian Booth (wallyworld)
milestone: none → 1.17.8
status: New → In Progress
importance: Undecided → Critical
tags: added: lxc regression
Ian Booth (wallyworld)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.17.8 → 1.19.0
Adam Stokes (adam-stokes)
tags: added: cloud-installer
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package juju-core - 1.18.0-0ubuntu1

---------------
juju-core (1.18.0-0ubuntu1) trusty; urgency=medium

  * New upstream release (LP: #1287147), including fixes for:
    - maas/lxc: LXC permission denied issue (LP: #1299588).
    - core: mega-watcher for machines does not include container
      addresses (LP: #1301464).
 -- James Page <email address hidden> Mon, 07 Apr 2014 18:24:59 +0100

Changed in juju-core (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Curtis Hovey (sinzui) wrote :

I lowered the trunk task to High because the fix was delivered to users in 1.18.0

Changed in juju-core:
importance: Critical → High
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.