Comment 3 for bug 1678339

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.