functional-container-networking-lxd fails with invalid parent device name
Bug #1581627 reported by
Andrew McDermott
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Andrew McDermott | ||
Bug Description
This CI test fails when the address-allocation feature flag is enabled. This is because although we have a list of interfaces to write for the LXD container configuration the setup in this case (address-allocation enabled) does not have a suitable parent device defined, hence the message "invalid parent device" when looking at the juju status output.
Revision history for this message
| Andrew McDermott (frobware) wrote | #1 |
| Changed in juju-core: | |
| status: | New → In Progress |
Revision history for this message
| Andrew McDermott (frobware) wrote | #2 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| milestone: | none → 2.0-beta9 |
| importance: | Undecided → Medium |
| importance: | Medium → High |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0-beta9 → none |
| milestone: | none → 2.0-beta9 |
To post a comment you must log in.
WIP - https:/