moving a subnet to a different fabric prevents DHCP relay configuration
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Triaged
|
Low
|
Unassigned | ||
| maas-ui |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Hello,
When configuring DHCP relay on MAAS, if a relay is configured on a VLAN, for example VLAN 41, with a subnet, for example 10.10.21.0/24. If that subnet is then moved to a different fabric, its not possible to disable the relay. The following warning is shown on the MAAS UI:
"No subnets are available on this VLAN. DHCP cannot be enabled." Although the UI shows as DHCP enabled.
[Steps to reproduce]
1. Setup maas with two VLANs, one untagged, one native VLAN for example VID 41, the native VLAN having DHCP forwarded to the untagged VLAN.
2. Setup a DHCP relay to go from 41, to untagged.
3. Configure DHCP relay for VLAN 41 via untagged along with a dynamic range.
4. Create a new fabric, and move the subnet for VLAN 41 to this subnet.
5. Try to disable DHCP relay on VLAN 41.
[Workaround]
Move the subnet back to its original VLAN, and disable DHCP first.
Thanks,
Peter
| summary: |
- moving to a different subnet prevents DHCP relay configuration + moving a subnet to a different fabric prevents DHCP relay configuration |
| Changed in maas: | |
| status: | New → Triaged |
| Changed in maas: | |
| milestone: | none → 3.5.0 |
| importance: | Undecided → Low |
| Thorsten Merten (thorsten-merten) wrote | #2 |
| Changed in maas-ui: | |
| importance: | Undecided → Low |
| milestone: | none → 3.5.0 |
| status: | New → Triaged |
This limitation exists only in the UI, it's possible to remove the DHCP relay settings using the CLI:
maas $ADMIN vlan update $FABRIC_ID $VID relay_vlan=