[2.2] Django interface update signal handlers are too opaque
Bug #1685963 reported by
Mike Pontillo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Mike Pontillo |
Bug Description
MAAS often takes action based on event-driven changes to Django models, such as pre-save, post-save, post-delete, or based on a particular field changing.
When bugs occur due to the actions these signal handlers take, they are often difficult to debug, since the work of the signal handler may be unrelated to the user's intended action.
For support purposes, logging should be added when a signal handler makes changes to the database.
Related branches
lp:~mpontillo/maas/signal-handlers-add-logging--bug-1685963
- Blake Rouse (community): Approve
-
Diff: 157 lines (+39/-16)1 file modifiedsrc/maasserver/models/signals/interfaces.py (+39/-16)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Mike Pontillo (mpontillo) |
milestone: | none → 2.2.0rc3 |
summary: |
- [2.2] Django signal handlers are too opaque + [2.2] Django interface update signal handlers are too opaque |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.