conflict when managing LXD storage with Juju 2.0
Bug #1573681 reported by
James Page
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned | ||
LXD Charm |
Fix Released
|
Medium
|
Unassigned | ||
nova-lxd |
Fix Released
|
Medium
|
Unassigned | ||
lxd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The lxd charm is designed to be placed on bare-metal alongside the nova-compute charm (or insert you charm here - its not fixed).
During configuration it will configure LXD with an appropriate storage backend based on end-user configuration supplied.
However, with Juju 2.0, its possible that Juju will also be trying to manage LXD containers on the same physical host - the act of reconfiguring the storage for LXD can break that and cause Juju's LXD container units to fail to provision.
tags: | added: kanban-cross-team |
tags: | added: landscape |
tags: | removed: kanban-cross-team |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: juju-release-support lxd |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | none → 2.1.0 |
Changed in charm-lxd: | |
status: | New → Triaged |
Changed in nova-lxd: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in charm-lxd: | |
importance: | Undecided → Medium |
no longer affects: | charms |
tags: | added: uosci |
Changed in juju: | |
status: | Triaged → Incomplete |
Changed in nova-lxd: | |
status: | Fix Committed → Fix Released |
Changed in charm-lxd: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Note that with Juju 1.25, this is not an issue as LXC containers are created and managed quite differently to LXD containers, so no conflict occurs.