LXC permission denied issue with 1.17.7
Bug #1299588 reported by
Nicolas Thomas
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Ian Booth | ||
1.18 |
Fix Released
|
Critical
|
Ian Booth | ||
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 modifiedworker/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 modifiedworker/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)
tags: | added: micro-cluster |
tags: | added: landscape |
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 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
milestone: | 1.17.8 → 1.19.0 |
tags: | added: cloud-installer |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.