"Enable DHCP" on VLAN does not setup a Reserved Dynamic range for secondary (IPv6) subnets
Bug #1583395 reported by
Trent Lloyd
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Opinion
|
Undecided
|
Unassigned |
Bug Description
When you "Enable DHCP" on a VLAN for the first time, a reserved range for dynamic usage is created. This occurs when enabling DHCP for either a single IPv4 or a single IPv6 subnet on a VLAN.
If you have two subnets on the VLAN, specifically both an IPv4 and IPv6 subnet, a reserved range for the secondary subnet is not request or setup. Only a single reserved range request is shown and made.
This occurs both during initial creation and during reconfiguration.
Version: xenial/main 2.0.0~beta3+
Changed in maas: | |
status: | New → Triaged |
milestone: | none → 2.0.0 |
Changed in maas: | |
milestone: | 2.0.1 → next |
Changed in maas: | |
milestone: | next → none |
To post a comment you must log in.
Related to this.. if the IPv6 subnet does not have a gateway, then you actually get a selector for which subnet to use. If you select the IPv4 subnet then nothing else shows, but if you select the IPv6 subnet it asks to enter the gateway.
If both have a gateway the subnet selector does not appear (just rack controller)
This feels related so adding here instead of filing separate, but can file separately if needed.