[astute] puppet logs without enabled "Openstack debug" non-informative.

[Sergey Vasilenko]

Puppet logs without enabled "Openstack debug" non-informative.
But with enabled debug free disk space ends very quickly.

I propose 2 stage way for fix it:

stage #1: Enable debug for all puppet calls

stage #2: extracted into separate ticket https://bugs.launchpad.net/fuel/+bug/1433092

[Dmitry Pyzhov (dpyzhov)]

It is hard to debug issues without it

[Sergey Vasilenko (xenolog)]

I think we should implement stage#1 before HCF 5.1

[Mike Scherbakov (mihgen)]

Folks, is this a blocker for HCF? Is there a possibility to track it in 6.0, and, if occasionally we get someone to fix it in 5.1 - then it's great. However we just have a lot of bugs left still which prevent us from HCF call. I believe this is not the one which really blocks us from the release....

[Sergey Vasilenko (xenolog)]

I think it's a blocker, because:
* all our tests running with enabled debug
* puppet logs without debug are unusible. After release our support team may be overloaded by logs with disabled debug and we will can't help them.

I belive, that fix for stage#1 contains 1 line of code.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/116585
Committed: https://git.openstack.org/cgit/stackforge/fuel-astute/commit/?id=bc60b7d027ab244039f48c505ac52ab8eb0a990c
Submitter: Jenkins
Branch: master

commit bc60b7d027ab244039f48c505ac52ab8eb0a990c
Author: Vladimir Sharshov <email address hidden>
Date: Mon Aug 25 14:59:54 2014 +0400

    Temporarily lock puppet debug in true state

    Change-Id: I7e5edab757802eaafc797b76c1b7b57dcb90f01e
    Closes-Bug: #1343136

[Vladimir Sharshov (vsharshov)]

Temporary fix present in 5.1 and 6.0:

https://github.com/stackforge/fuel-astute/commit/bc60b7d027ab244039f48c505ac52ab8eb0a990c

[Vladimir Sharshov (vsharshov)]

Related with: https://bugs.launchpad.net/fuel/+bug/1390436

[Bogdan Dobrelya (bogdando)]

@Vladimir could you please provide an update for 6.1 fix?

[Bogdan Dobrelya (bogdando)]

As we have this fix in master as well https://github.com/stackforge/fuel-astute/blob/master/lib/astute/puppet_task.rb#L88
the status of this bug is fix committed for 5.1, 6.0, .6.1

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/162909

[OpenStack Infra (hudson-openstack)]

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

[Evgeniy L (rustyrobot)]

The task consists of two stages, first stage was implemented, but second was not implemented.
It's not clear if UI configuration should be backported, if it should then data migration is required.

[Evgeniy L (rustyrobot)]

Moving tasks to In Progress.

[Evgeniy L (rustyrobot)]

I've just figured out that we don't do data migration in minor updates, hence the second part cannot be implemented.

[Evgeniy L (rustyrobot)]

Extracted second stage into the ticket https://bugs.launchpad.net/fuel/+bug/1433092 and removing "stage #2: add select-box "Deployment process debug" to the UI, enabled by default." from the description.

[Evgeniy L (rustyrobot)]

Set triaged for 5.1 and 6.0 to triaged, because patch is not backported https://review.openstack.org/#/c/116585/

[Vladimir Sharshov (vsharshov)]

Patch https://review.openstack.org/#/c/116585/ was merged Aug 25, 2014. Release 5.1, 6.0 and 6.1 included. Move it to
Fix Released for first stage.

Second stage moved to separate part: https://bugs.launchpad.net/fuel/+bug/1433092