Commissioning fails if use_rack_proxy is False
Bug #1938816 reported by
Björn Tillenius
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Björn Tillenius | ||
Bug Description
With current master, 0352fa02b20c9e3
The reason is that 0e490fcb9406125
The problem is that MAAS_BASE_URL points to the metadata endpoint. If use_rack_proxy is True, it will point to the rack, and if it's False, it will point to the region. But the resource binary is only available from the rack.
Related branches
~bjornt/maas:machine-resources-metadata
- Adam Collard (community): Approve
- MAAS Lander: Approve
-
Diff: 166 lines (+41/-14)7 files modifieddebian/maas-common.install (+8/-0)
debian/python3-maas-provisioningserver.install (+0/-8)
src/maasserver/webapp.py (+7/-0)
src/metadataserver/builtin_scripts/commissioning_scripts/50-maas-01-commissioning (+1/-1)
src/provisioningserver/rackdservices/http.py (+2/-5)
src/provisioningserver/utils/fs.py (+9/-0)
src/provisioningserver/utils/tests/test_fs.py (+14/-0)
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in maas: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Björn Tillenius (bjornt) |
| Changed in maas: | |
| milestone: | none → next |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| milestone: | next → 3.1.0-beta1 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
