Merge ~bjornt/maas:bug-1992330-3.2 into maas:3.2
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Björn Tillenius | ||||
Approved revision: | 6c309c32f2b2e4b68041a8be938b09674b68cab8 | ||||
Merge reported by: | MAAS Lander | ||||
Merged at revision: | not available | ||||
Proposed branch: | ~bjornt/maas:bug-1992330-3.2 | ||||
Merge into: | maas:3.2 | ||||
Diff against target: |
201 lines (+60/-44) 4 files modified
src/maasserver/dhcp.py (+5/-34) src/maasserver/models/subnet.py (+9/-4) src/maasserver/models/tests/test_subnet.py (+4/-4) src/maasserver/tests/test_dhcp.py (+42/-2) |
||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Björn Tillenius | Approve | ||
Review via email: mp+433102@code.launchpad.net |
Commit message
Don't return ipv6 boot addresses for ipv4 subnets.
An ipv4 subnet won't be able to use ipv6 addresses, and it would break the
DHCP config.
(cherry picked from commit 425a78cfd666e05
LP #1992330: Use the rack controller IP as DNS when relaying DHCP
Add relay rack ips as DNS servers
This patch aims to add the rack controll IP addresses of the relay
vlan as DNS servers.
This fixes an issue that when there are no other settings or available
IPs, MAAS adds only the IP address of the region controller, but
sometimes the region controller might not be routed to that vlan, hence
this patch, as the rack controllers should always be reachable by the
machines.
(cherry picked from commit 65a0cacf6aa3770
Self-approve backport