Why does MAAS need to assign a new IP to the machine during the deployment process?
Host A: 192.168.35.20( external dhcp)
MAAS successfully commissions Host A with this IP(20). When I start the deployment process for Host A, MAAS assigns a random IP to this machine from DHCP and finishes the deployment process. If there is no free IP in the DHCP pool, “connection timeout” occurs at the cloud-init target stage. Is there a way to make MAAS use Host A’s already assigned IP(.20)?
By determining the DHCP range, I ensure that MAAS assigns an IP from the range I want temporarily, but why does it need to change the IP that is already assigned?