Comment 0 for bug 1068843

Context is the QA lab

In one VM I have the region-controller (RC) where:

10.98.0.90 is the api/webui
192.168.21.5 is the RC's provisioning server

On another VM I have a cluster-controller (CC) where

192.168.20.5 is the CC's provisioning server
10.98.0.91 is the interface connected to the RC network

The 21.x and 20.x networks don't have access to each other.

When I install the CC, I set up the API to http://10.98.0.90/MAAS

When the CC is registered to the RC and and dhcpd.conf file is written, I get this:

subnet 192.168.20.0 netmask 255.255.255.0 {
       next-server 192.168.21.5;
       filename "pxelinux.0";
       option subnet-mask 255.255.255.0;
       option broadcast-address 192.168.20.255;
       option domain-name-servers 192.168.21.5;
       option routers 192.168.20.1;
       range dynamic-bootp 192.168.20.10 192.168.20.20;
}

When the nodes in the 20.x network are booted, they can reach the DHCP server but can't reach the provisioning server.
If I change the next-server value to 192.168.20.5, the nodes can't find the images.

Looks like when the CC is registered, the images in the RC should be sent to the CC, so it can serve them to the nodes in its network.