stats-report doesn't do a good job of error reporting
Bug #612722 reported by
gholt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Low
|
Greg Lange |
Bug Description
stats-report, when things are going wrong, doesn't do a good job of helping track down the problem. For instance, 404s and 507s are completely muted with no options to reenable them. It be nice to be able to run in a debug-mode to tell which devices are 404/507ing.
Changed in swift: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in swift: | |
assignee: | nobody → Greg Lange (greglange) |
Changed in swift: | |
milestone: | none → 1.6.0 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm looking at the stats-report and considering refactoring it.
I'm new to Python, but I don't see any tests for this executable.
If you have an opinion about how this should work or be made better, let me know. (or any tips on testing python)