tripleo

puppet log folder is empty

Bug #1536009 reported by Removed by request
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Heat Templates
Fix Released
Medium
Alex Schultz
tripleo
Fix Released
Medium
Alex Schultz
tripleo ocata-1 "ocata-1"

Bug Description

When using puppet in TripleO deployments/, even if logdir is configured /var/log/puppet has nothing in it, so if a deployment has failed a user has no idea what went wrong from the puppet logs.
Things that an end-user would want to see here:
  Standard output still going into a log.
  The ability to pass pre-deployment a --verbose and --debug flags to 'puppet apply'.

Tags: puppet
Sanjay Upadhyay (saneax)
Changed in tripleo:
status: New → Confirmed
Revision history for this message
Alex Schultz (alex-schultz) wrote :

related patch, https://review.openstack.org/388210

Changed in tripleo:
milestone: none → ocata-1
importance: Undecided → Medium
assignee: nobody → Alex Schultz (alex-schultz)
Revision history for this message
Steven Hardy (shardy) wrote :

Can we close this now https://review.openstack.org/#/c/388210/ landed, so passing ConfigDebug: true in an environment file should enable the local logging feature in the heat hook?

Changed in heat-templates:
assignee: nobody → Alex Schultz (alex-schultz)
importance: Undecided → Medium
status: New → Fix Released
Changed in tripleo:
status: Confirmed → Incomplete
milestone: ocata-1 → ocata-2
Revision history for this message
Alex Schultz (alex-schultz) wrote :

Yes, setting ConfigDebug: true will trigger local puppet logging with that change.

Changed in tripleo:
status: Incomplete → Fix Released
Steven Hardy (shardy)
Changed in tripleo:
milestone: ocata-2 → ocata-1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.