upgraded juju from 2.0.0: nodes allocation fails if any bridge created in MAAS
Bug #1656304 reported by
Alvaro Uria
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned |
Bug Description
Juju 2.0.2
MaaS 2.1.1+bzr5544-
Steps to reproduce:
1) create a bridge for one or all the interfaces gathered after Commissioning phase
2) juju deploy cs:xenial/ubuntu
Node in Ready state gets allocated, and briefly moves to Deploying status to go back to Ready state. Node gets powered on ("power off" is not triggered).
If we remove all bridges created in maas, node gets deployed OK (br-$ifacename is created).
The behavior above is not documented and doesn't allow nodes to have multiple bridges (ie. br0-mgmt, with an assigned IP + br1-pub, unconfigured bridge for LXDs).
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.2.0 |
summary: |
- juju2/maas2: nodes allocation fails if any bridge created in MAAS + upgraded juju from 2.0.0: nodes allocation fails if any bridge created + in MAAS |
Changed in juju: | |
status: | New → Triaged |
Changed in juju: | |
milestone: | 2.2-beta1 → 2.2-beta2 |
Changed in juju: | |
milestone: | 2.2-beta2 → 2.2-beta3 |
Changed in juju: | |
milestone: | 2.2-beta3 → 2.2-beta4 |
Changed in juju: | |
milestone: | 2.2-beta4 → 2.2-rc1 |
To post a comment you must log in.
We track Juju 2.x issues in "juju" project. Re-targeting :)