[2.2] Can't assign a static IP to a physical interface due to incorrect validation

Bug #1678339 reported by Mike Pontillo on 2017-03-31
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Mike Pontillo
2.2
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

Mike Pontillo (mpontillo) wrote :
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 :

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.

Changed in maas:
status: Triaged → Won't Fix
milestone: 2.2.0rc1 → none
Mike Pontillo (mpontillo) wrote :

I disagree. It's fine if MAAS does not "support" this configuration (per se), but that's different than creating a validation to actively prevent it for no good reason, which is MAAS's current behavior.

I don't think it makes sense to allow MAAS to enable DHCP on a tagged VLAN, if you cannot subsequently allow a node to boot off of that VLAN in an untagged configuration. A network boot is almost always going to support this. There is no reason to have this validation.

The MAAS rack is fully trunked, as recommended. But there is no possible way to configure this node to share a default "untagged" VLAN with MAAS *AND* allow it to PXE boot.

tags: removed: regression
Dean Henrichsmeyer (dean) wrote :

Agreed. Not supporting it and preventing it are two different things.

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers