CentOS deployments should use rack controller as built-in proxy server
Bug #1896541 reported by
Jose Delarosa
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
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:/
Changed in maas: | |
milestone: | none → 2.9.0b4 |
status: | New → Triaged |
tags: | added: seg sts |
Changed in maas: | |
milestone: | 2.9.0b4 → 2.9.0b7 |
Changed in maas: | |
milestone: | 2.9.0b7 → 2.9.x |
Changed in maas: | |
milestone: | 2.9.2 → 2.9.x |
Changed in maas: | |
milestone: | 2.9.x → none |
status: | Triaged → Fix Released |
Changed in maas: | |
milestone: | none → 2.9.0 |
To post a comment you must log in.
I'll be curious to see if you can reproduce the issue using 2.9 PPA : /launchpad. net/~maas/ +archive/ ubuntu/ 2.9 (As of today '1:2.9. 0~beta5- 8994-g. 8eaf8a312- 0ubuntu1~ 20.04.1' )
https:/
References: /bugs.launchpad .net/maas/ +bug/1881133 /github. com/maas/ maas/commit/ a44d3a8a62be1d2 db4af9de27fdf41 4bcd45fc1a
https:/
https:/
--
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