[2.5b3] Unable to deploy server - curtin config SERVER_ROOT
Bug #1798479 reported by
Mark Shuttleworth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Newell Jensen |
Bug Description
With a freshly upgraded MAAS 2.5b3 I'm unable to deploy servers, seeing this error:
Error: Node failed to be deployed, because of the following error: Failed to retrieve curtin config: 'SERVER_PORT'
Related branches
~newell-jensen/maas:lp1798479
Merged
into
maas:master
- Lee Trager (community): Approve
- Andres Rodriguez (community): Approve
- MAAS Lander: Approve
-
Diff: 115 lines (+45/-7)3 files modifiedsrc/maasserver/node_action.py (+2/-1)
src/maasserver/websockets/protocol.py (+20/-4)
src/maasserver/websockets/tests/test_protocol.py (+23/-2)
Changed in maas: | |
milestone: | none → 2.5.0rc1 |
importance: | Undecided → Critical |
Changed in maas: | |
assignee: | nobody → Newell Jensen (newell-jensen) |
status: | New → Triaged |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 2.5.0rc1 → 2.5.0beta4 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hi Mark,
Is this something you can constantly reproduce? Were all region/rack controllers connected at the time? Are you accessing MAAS over a VIP, reverse proxy or similar ?
The reason I ask is because it seems like a similar issue we have fixed before [1], which would have prevented all machine deployments. That said, the code should have obtained the SERVER_PORT from the request.
[1]: https:/ /code.launchpad .net/~newell- jensen/ maas/+git/ maas/+merge/ 355997