tgt-admin exceptions aren't logging error response
Bug #1186991 reported by
John Griffith
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Fix Released
|
High
|
Avishay Traeger | ||
Bug Description
We're catching exceptions from calls to tgt-admin and handling them well enough, however there are a number of places where we're not providing the error response info (from the tgt-admin call) anywhere in the logs.
This makes debug a bit of a guessing game. We should add the error response from the ProcessExecution exception to the log output.
| Changed in cinder: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Avishay Traeger (avishay-il) |
| milestone: | none → havana-2 |
| tags: | added: grizzly-backport-potential |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to cinder (master) | #1 |
| Changed in cinder: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to cinder (master) | #2 |
| Changed in cinder: | |
| status: | In Progress → Fix Committed |
| Changed in cinder: | |
| status: | Fix Committed → Fix Released |
| Changed in cinder: | |
| milestone: | havana-2 → 2013.2 |
| tags: | removed: grizzly-backport-potential |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/