The mistral-db-manage should log it's output
Bug #1689821 reported by
Dougal Matthews
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
High
|
Adriano Petrich |
Bug Description
Currently the mistral-db-manage command doesn't log it's output - so unless you happen to keep the stdout, then it will be lost.
This can be a problem if there is an error, for example, in action loading.
It should be setup so that logging to a file with the other mistral logs is done. This could be optional if it isn't generally wanted, but the file should be much smaller than all of the others.
Recently a TripleO issue couldn't be found easily because the command didn't log any output.
Changed in mistral: | |
assignee: | nobody → Adriano Petrich (apetrich) |
Changed in mistral: | |
milestone: | none → pike-2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/464010
Review: https:/