StateNotFoundError exception class needs to be more flexible
Bug #1225701 reported by
Thomi Richards
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Autopilot |
Fix Released
|
High
|
Unassigned | ||
autopilot (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Currently we only tell the user about the class name and id when raising a StateNotFoundError exception instance. Since we're not using this in places where the query parameters are passed in by the teast author, the exception message isn't very useful. We should instead report *all* the filter parameters that were used when we failed to find new state.
Related branches
lp:~thomir-deactivatedaccount/autopilot/fix-state-not-found
- Martin Pitt (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 165 lines (+124/-10)2 files modifiedautopilot/introspection/dbus.py (+49/-10)
autopilot/tests/unit/test_exceptions.py (+75/-0)
Changed in autopilot: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix committed into lp:autopilot/1.3 at revision 327, scheduled for release in autopilot, milestone Unknown