Merge ~andreserl/maas:lp1548402 into maas:master
Proposed by
Andres Rodriguez
Status: | Merged |
---|---|
Merge reported by: | Andres Rodriguez |
Merged at revision: | 68948d1f59b3f1c3b482a36ef423e9c850b18d8d |
Proposed branch: | ~andreserl/maas:lp1548402 |
Merge into: | maas:master |
Diff against target: |
42 lines (+13/-0) 2 files modified
src/maasserver/api/machines.py (+7/-0) src/maasserver/node_action.py (+6/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Blake Rouse (community) | Needs Fixing | ||
Newell Jensen (community) | Needs Fixing | ||
Review via email: mp+327054@code.launchpad.net |
Commit message
LP: #1548402 - Handle errors in preseeds
Ensure that MAAS prevents starting the deployment of a machine if the preseeds fail to render.
To post a comment you must log in.
So I have a few questions here:
1. Should we prevent if all the curtin preseed rendering fails, or only if curtin_userdata ?
2. Raising the error via the API forms causes an issue we have discussed before, which is some errors so in json format (like {"distro_series": ["'asdfadsf' is not a valid distro_series... ']} ) but this would show as plain text. Since we discussed plain output vs structured output... how should we handle this?
3. Why do we have different actions for the API vs the UI? It would seem to me that deploying via the UI should be done exactly like the API.