Subnet-Test2:10.12.19.0/24 is what I have referred to in this case as subnet C
Subnet-OSMgmt:10.12.15.0/24 is what I have referred to in this case as subnet B
from the cli "maas admin subnets read" I the same primary and secondary rack controllers for both subnets.
The workaround we found was to explicitly set the DNS servers on subnet C to point to the rack controllers. But I expected it to point to the rack controllers by default.
In my test environment:
>>> Subnet. objects. get_best_ subnet_ for_ip( '10.12. 19.7') Test2:10. 12.19.0/ 24(vid= 19)> objects. get_best_ subnet_ for_ip( '10.12. 15.7') OSMgmt: 10.12.15. 0/24(vid= 15)>
<Subnet: Subnet-
>>> Subnet.
<Subnet: Subnet-
Subnet- Test2:10. 12.19.0/ 24 is what I have referred to in this case as subnet C OSMgmt: 10.12.15. 0/24 is what I have referred to in this case as subnet B
Subnet-
from the cli "maas admin subnets read" I the same primary and secondary rack controllers for both subnets.
The workaround we found was to explicitly set the DNS servers on subnet C to point to the rack controllers. But I expected it to point to the rack controllers by default.