[2.1] bridge_all on allocate needs to bridge all unconfigured interfaces too
Bug #1625636 reported by
Andrew McDermott
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Critical
|
Unassigned | ||
Bug Description
Juju is currently bridging all interfaces, even those that are unconfigured, to ensure that interface devices are available in a container. Juju was previously only bridging active/configured interfaces but this did not satisfy the Neutron/LXD case.
With MAAS 2.1 Juju wants to switch to using bridge_all but we now need bridge_all to bridge all interfaces the node has (configured and unconfigured).
| summary: |
- [2.1] bridge_all on allocate should bridge all unconfigured interfaces + [2.1] bridge_all on allocate doens't bridge all unconfigured interfaces too |
| Changed in maas: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
| milestone: | none → 2.1.0 |
| tags: | added: juju |
| Changed in maas: | |
| importance: | Wishlist → Critical |
| summary: |
- [2.1] bridge_all on allocate doens't bridge all unconfigured interfaces + [2.1] bridge_all on allocate needs to bridge all unconfigured interfaces too |
| Changed in maas: | |
| status: | Confirmed → Triaged |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #1 |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #2 |
| Changed in maas: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
After discussion, it was agreed that juju will only bridge interfaces that have IP address. In 2.1. MAAS currently only bridges interfaces that are configured with either:
1. auto assign
2. static assign
3. DHCP.