CentOS deployments should use rack controller as built-in proxy server

[Jose Delarosa]

In MAAS v2.7 and v2.8 (where it was tested - could also impact v2.6), for machines deployed with Ubuntu, the built-in proxy server is set to the _rack_ controller, whereas in machines deployed with CentOS, it is set to the _region_ controller. This is a problem in deployments where deployed CentOS machines do not have network connectivity to the region controller.

From https://github.com/maas/maas/blob/master/src/maasserver/compose_preseed.py#L68-L97, looks like config["use_rack_proxy"] should be set for CentOS deployments.

[Eric Desrochers (slashd)]

I'll be curious to see if you can reproduce the issue using 2.9 PPA :
https://launchpad.net/~maas/+archive/ubuntu/2.9 (As of today '1:2.9.0~beta5-8994-g.8eaf8a312-0ubuntu1~20.04.1')

References:
https://bugs.launchpad.net/maas/+bug/1881133
https://github.com/maas/maas/commit/a44d3a8a62be1d2db4af9de27fdf414bcd45fc1a
--
Author: Lee Trager <email address hidden>
Date: Fri Aug 14 18:49:31 2020 +0000

LP: #1881133 - Always include rack controller IPs for DNS servers.

MAAS was only including the configured URL for controllers which did not
always include all rack controllers the VLAN is configured to use. This
would also sometimes include the region controller's IP even when the
machine is unable to directly access the rack controller.

--

# git describe --contains a44d3a8a6
2.9.0-beta1~82

[Eric Desrochers (slashd)]

After some testing made by Jose (the reporter of this bug)...

It looks like the issue is resolved with MAAS v2.9 (MAAS version: 1:2.9.0~beta6 (9039-g.5a2ba747e-0ubuntu1~20.04.1).