The mistral-db-manage should log it's output

[Dougal Matthews]

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.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/464010

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/464010
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=4c53234e271a6a803d0f9fb83de5dacbe3d7efff
Submitter: Jenkins
Branch: master

commit 4c53234e271a6a803d0f9fb83de5dacbe3d7efff
Author: Adriano Petrich <email address hidden>
Date: Thu May 11 15:46:25 2017 +0100

    Adding log to db_sync

    if called by mistral-db-manage it will log info level
        to /var/log/mistral/mistral-db-manage

    Included some debug level logging also for main actions.

    Change-Id: I0574b38efcc0dd7485953bf3089ff0a5a3ef6394
    Closes-Bug: #1689821

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/mistral 5.0.0.0b2 development milestone.