[2.2] Can't assign a static IP to a physical interface due to incorrect validation
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Mike Pontillo | ||
| 2.2 |
Fix Released
|
High
|
Mike Pontillo | ||
Bug Description
I have MAAS installed on my home router in a LXD container.
My MAAS network is configured on a separate VLAN than the default untagged VLAN on the home router, so that wired and wireless traffic on my home network can be kept separate from network traffic for MAAS deployments.
MAAS works great in this scenario, except for one quirk: I can't edit any of my machines' physical interfaces. This is because MAAS makes the incorrect assumption that physical interfaces on machines cannot have a different default VLAN than the MAAS rack controller.
When I commission a machine, MAAS correctly determines that (from the rack controller point of view) the machine's interfaces are on VLAN 100.
The problem comes when I try to change *anything* about the interface, such as assign it a static IP address. Then MAAS presents me with an error that cannot be worked around. (See attached screenshot. I didn't change the VLAN in this case.)
Related branches
- Andres Rodriguez (community): Approve
-
Diff: 764 lines (+103/-161)4 files modifiedsrc/maasserver/api/tests/test_interfaces.py (+13/-22)
src/maasserver/forms/interface.py (+2/-21)
src/maasserver/forms/tests/test_interface.py (+65/-94)
src/maasserver/websockets/handlers/tests/test_machine.py (+23/-24)
- Mike Pontillo (community): Approve
-
Diff: 764 lines (+103/-161)4 files modifiedsrc/maasserver/api/tests/test_interfaces.py (+13/-22)
src/maasserver/forms/interface.py (+2/-21)
src/maasserver/forms/tests/test_interface.py (+65/-94)
src/maasserver/websockets/handlers/tests/test_machine.py (+23/-24)
| Mike Pontillo (mpontillo) wrote | #1 |
| description: | updated |
| description: | updated |
| Changed in maas: | |
| milestone: | none → 2.2.0rc1 |
| importance: | Undecided → Critical |
| status: | New → Triaged |
| tags: | added: regression |
| Andres Rodriguez (andreserl) wrote | #2 |
| Changed in maas: | |
| status: | Triaged → Won't Fix |
| milestone: | 2.2.0rc1 → none |
| Mike Pontillo (mpontillo) wrote | #3 |
| tags: | removed: regression |
| Dean Henrichsmeyer (dean) wrote | #4 |
| Changed in maas: | |
| milestone: | none → 2.3.0 |
| importance: | Critical → High |
| status: | Won't Fix → Triaged |
| Changed in maas: | |
| assignee: | nobody → Mike Pontillo (mpontillo) |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| milestone: | 2.3.0 → 2.3.0alpha1 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
| tags: | added: 4010 |
After discussion over IRC it was determined that in reality, the switch port connected to eno1 is actually configured for VLAN100. This means that the switch is "clamped". MAAS doens't support clamping.