FAN - unable to setup network
Bug #1722661 reported by
james beedy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Witold Krecicki | ||
Bug Description
Container fails to start when deployed to an instance that was deployed with a "spaces" constraint (machine 0).
Looks like everything checks out when the container is deploy to the instance without the "spaces" constraint (machine 1).
juju status <- http://
juju status --format yaml <- http://
| description: | updated |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Witold Krecicki (wpk) |
| milestone: | none → 2.3-beta2 |
| Changed in juju: | |
| status: | Triaged → In Progress |
Revision history for this message
| Witold Krecicki (wpk) wrote | #1 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The problem was with FAN subnet not inheriting the underlaying network space - https:/