Deploy user_data expects binary string
Bug #1885237 reported by
Huw Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Adam Collard | ||
Bug Description
When passing user_data to the deploy action from the websocket API it returns an error that the string must be a binary string.
Also, is there any way to access the user_data post deploy? Is it stored somewhere I've missed. In the new UI there will be a modal to show what the machine was deployed with (linked from the machine list and machine details).
Related branches
~adam-collard/maas:user-data-encoding-1885237
- MAAS Lander: Approve
- Alberto Donato (community): Approve
-
Diff: 55 lines (+8/-2)2 files modifiedsrc/maasserver/node_action.py (+5/-1)
src/maasserver/tests/test_node_action.py (+3/-1)
Revision history for this message
| Lee Trager (ltrager) wrote | #1 |
| Changed in maas: | |
| assignee: | nobody → Lee Trager (ltrager) |
Revision history for this message
| Huw Wilkins (huwshimi) wrote | #2 |
| Changed in maas: | |
| status: | New → Invalid |
| status: | Invalid → New |
Revision history for this message
| Huw Wilkins (huwshimi) wrote | #3 |
| Changed in maas: | |
| milestone: | none → 2.9.0b1 |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in maas: | |
| assignee: | Lee Trager (ltrager) → Adam Collard (adam-collard) |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I mentioned to Amy that MAAS should accept base64 or plain text user_data. We should do this on both the API and for the websocket.