Fix the way in which execute() errors are detected and managed
Bug #1346879 reported by
Amrith Kumar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Medium
|
Amrith Kumar |
Bug Description
When using execute() or execute_
trove/guestagen
This bug is to find and fix these incorrect usages.
Changed in trove: | |
assignee: | nobody → Amrith (amrith) |
Changed in trove: | |
importance: | Undecided → Medium |
milestone: | none → juno-3 |
Changed in trove: | |
status: | In Progress → Fix Committed |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | juno-3 → 2014.2 |
To post a comment you must log in.
Do you mean add check_exit_code parameter to each exec?