LXD & block storage: unit agent never runs
Bug #1799989 reported by
Cory Johns
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
See this trivial test charm: https:/
Deploying that on the LXD provider without explicitly attaching storage causes the unit agent to be stuck at "allocating": https:/
Per discussion with Ian, it seems that this has to do with the security concerns around passing block devices into containers, as discussed here: https:/
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.5-beta1 |
assignee: | nobody → Joseph Phillips (manadart) |
Changed in juju: | |
milestone: | 2.5-beta1 → 2.5-beta2 |
Changed in juju: | |
milestone: | 2.5-beta2 → 2.5-beta3 |
Changed in juju: | |
milestone: | 2.5-beta3 → 2.5-rc1 |
Changed in juju: | |
milestone: | 2.5-rc1 → 2.5.1 |
Changed in juju: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in juju: | |
assignee: | Joseph Phillips (manadart) → nobody |
Changed in juju: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in juju: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in juju: | |
milestone: | 2.5.4 → 2.5.5 |
Changed in juju: | |
milestone: | 2.5.6 → 2.5.8 |
Changed in juju: | |
milestone: | 2.5.8 → 2.5.9 |
To post a comment you must log in.
Machine log looks like this: /pastebin. ubuntu. com/p/vQCtphkh5 k/
https:/