Merge lp:~gmb/maas/rpc-error-handling-middleware into lp:~maas-committers/maas/trunk
Proposed by
Graham Binns
Status: | Merged |
---|---|
Approved by: | Graham Binns |
Approved revision: | no longer in the source branch. |
Merged at revision: | 3128 |
Proposed branch: | lp:~gmb/maas/rpc-error-handling-middleware |
Merge into: | lp:~maas-committers/maas/trunk |
Diff against target: |
217 lines (+148/-2) 4 files modified
src/maas/settings.py (+1/-0) src/maasserver/middleware.py (+41/-0) src/maasserver/tests/test_middleware.py (+103/-0) src/provisioningserver/rpc/power.py (+3/-2) |
To merge this branch: | bzr merge lp:~gmb/maas/rpc-error-handling-middleware |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gavin Panella (community) | Approve | ||
Review via email: mp+236396@code.launchpad.net |
Commit message
Add middleware to handle errors from RPC connections.
At present, "handling" means "display an error message to the user". There may be a Better Way but this is a good start.
Description of the change
I've tested this on a local test rig with VMs, so I'm reasonably confident that it'll work fine. I'm not sure whether we should *also* be logging the errors to maas-django.log; that seems sane but there's already a lot of cruft in there.
To post a comment you must log in.
Looks good, but I think the handling of MultipleFailures needs changing.