puppet debug log is not enabled even when debug logging option is enabled

Bug #1289545 reported by Dmitry Borodaenko on 2014-03-07
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
High
Fuel Library (Deprecated)
4.1.x
High
Unassigned
5.0.x
High
Fuel Library (Deprecated)

Bug Description

The "OpenStack debug logging" option should not be limited to OpenStack. In particular, it is crucial to enable Puppet --debug and --evaltrace options to diagnose deployment problems. When this option is enabled (it should also be renamed to "Debug logging"), puppet apply command line should include --debug --evaltrace.

Changed in fuel:
status: New → Confirmed
Changed in fuel:
status: Confirmed → Triaged
milestone: 4.1.1 → 5.0
tags: added: backports-4.1.1
tags: added: low-hanging-fruit
Bogdan Dobrelya (bogdando) wrote :

Partially addressed by: https://review.openstack.org/#/c/88277/ (Add evaltrace, if debug)

Bogdan Dobrelya (bogdando) wrote :

According to https://github.com/stackforge/fuel-astute/blob/master/lib/astute/puppetd.rb#L51-56 we already have UI debug option passed as a puppet apply parameter, am I wrong?

Changed in fuel:
status: Triaged → Fix Committed
Bogdan Dobrelya (bogdando) wrote :

As far as I can see the astute part for debug logs for puppet already presents in stable/4.1 https://github.com/stackforge/fuel-astute/blob/stable/4.1/lib/astute/puppetd.rb#L51-56
So, the only action item left is to backport https://review.openstack.org/#/c/88277/ as well.

Bogdan Dobrelya (bogdando) wrote :

But the 88277 patch cannot be backported for 4.1.1 due to the puppet version we use for it - changes are unsupported. Hence, nothing to backport

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers