Merge lp:~julian-edwards/maas/bulk_action_error_catch into lp:~maas-committers/maas/trunk
Proposed by
Julian Edwards
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Julian Edwards | ||||
Approved revision: | no longer in the source branch. | ||||
Merged at revision: | 2428 | ||||
Proposed branch: | lp:~julian-edwards/maas/bulk_action_error_catch | ||||
Merge into: | lp:~maas-committers/maas/trunk | ||||
Diff against target: |
61 lines (+31/-2) 2 files modified
src/maasserver/forms.py (+12/-2) src/maasserver/tests/test_forms.py (+19/-0) |
||||
To merge this branch: | bzr merge lp:~julian-edwards/maas/bulk_action_error_catch | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jeroen T. Vermeulen (community) | Approve | ||
Review via email: mp+223345@code.launchpad.net |
Commit message
Ensure that BulkActionForm catches the new NodeActionError raised inside StartNode. Previously it resulted in an internal server error traceback.
To post a comment you must log in.
This is stretching the definition of "not actionable." You'll want to update the docstring for BulkNodeActionF orm.save: it still says that this outcome is for disallowed state transitions.
Exception safety w.r.t. NodeActionError is important here. You assume that the transaction will still be valid when this happens, which is not what you'd expect for your average exception coming out of the action. You're making this part of the contract for NodeAction.execute, so document it in the docstring.