apt proxy addr was hardencoded
This bug report will be marked for expiration in 49 days if no further activity occurs. (find out why)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
file: `/etc/apt/
log: ```
$ sudo apt update
Err:1 http://
Could not connect to 192.168.0.147:8000 (192.168.0.147). - connect (113: No route to host)
Err:2 http://
Could not connect to 192.168.0.147:8000 (192.168.0.147). - connect (113: No route to host)
Err:3 http://
Unable to connect to 192.168.0.147:8000:
Err:4 http://
Unable to connect to 192.168.0.147:8000:
Err:5 http://
Unable to connect to 192.168.0.147:8000:
Reading package lists... Done
Building dependency tree
Reading state information... Done
11 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://
W: Failed to fetch http://
W: Failed to fetch http://
W: Failed to fetch http://
W: Failed to fetch http://
W: Some index files failed to download. They have been ignored, or old ones used instead.
```
As shown above, the MAAS region controller's IP addr was hard-coded to the APT config. So if a secondary controller was removed from the cluster, deployed machines will be unable to perform APT updates/installs.
To solve this issue, create a dedicated DNS alias pointed to all running controllers, and use that alias as the proxy addr.
| Alexsander de Souza (alexsander-souza) wrote | #1 |
| Changed in maas: | |
| status: | New → Incomplete |
| maasuser1 (maasuser1) wrote | #2 |
what's the MAAS URL? (see /var/snap/