[2.3, 2.4, 2.5] On fresh install, maas_proxy_port was not set in squid config
Bug #1786526 reported by
Andres Rodriguez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Andres Rodriguez | ||
| 2.3 |
Fix Released
|
Medium
|
Andres Rodriguez | ||
| 2.4 |
Fix Released
|
Medium
|
Andres Rodriguez | ||
Bug Description
On a fresh install the proxy port was not set on the squid config
https:/
The strange thing is that the config was correctly rendered with the subnets, but not with the proxy port.
This could be because:
1. Something failed internally and was unable to get the config from the DB ?
2. The default value is not being set correctly ?
3. A failure caused that the value was not available?
Related branches
~andreserl/maas:lp1786526_2.3
- Andres Rodriguez (community): Approve
-
Diff: 16 lines (+4/-0)1 file modifiedsrc/provisioningserver/templates/proxy/maas-proxy.conf.template (+4/-0)
~andreserl/maas:lp1786526_2.4
- Andres Rodriguez (community): Approve
-
Diff: 16 lines (+4/-0)1 file modifiedsrc/provisioningserver/templates/proxy/maas-proxy.conf.template (+4/-0)
~andreserl/maas:lp1786526_proxy_port_failsafe
- Blake Rouse (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 16 lines (+4/-0)1 file modifiedsrc/provisioningserver/templates/proxy/maas-proxy.conf.template (+4/-0)
| Changed in maas: | |
| milestone: | none → 2.5.0alpha2 |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #1 |
| Changed in maas: | |
| assignee: | nobody → Andres Rodriguez (andreserl) |
| status: | New → In Progress |
| importance: | Undecided → High |
| importance: | High → Medium |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Workaround is to force the port:
maas <user> maas set-config name=maas_