Bug 1265356

Summary: RFE for debug output for puppet agent -t
Product: Red Hat OpenStack Reporter: Jeremy <jmelvin>
Component: openstack-puppet-modulesAssignee: Ivan Chavero <ichavero>
Status: CLOSED CANTFIX QA Contact: yeylon <yeylon>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.0 (RHEL 6)CC: ichavero, mmagr, srevivo, yeylon
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: 5.0 (RHEL 6)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-22 14:02:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeremy 2015-09-22 18:11:40 UTC 
Description of problem: 
RFE for more debug output for puppet agent -td. The customer would like to get more info with the facts being collected. So if it hangs getting info for a particular fact you can see it in the debug output. 



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: 
running puppet agent -td on forman server
Comment 1 Jeremy 2015-09-22 19:38:47 UTC 
This was the facter code which was hanging and causing puppet agent to hang completely with no indication of why:

# cat gettarball.rb
require 'facter'

Facter.add("prodtarball") do
        setcode do
                Facter::Util::Resolution.exec("/usr/bin/wget -O - 2>&1 ftp://iam-utility.lab.dev.us.ml.com/forwarders/ti-infra-forwarders/ | grep Linux-x86_64 | awk -F'>' '{print $2}'|awk -F'.gz' '{print $1}'")
        end
end
Facter.add("labtarball") do
        setcode do
                Facter::Util::Resolution.exec("/usr/bin/wget -O - 2>&1 ftp://iam-utility.lab.dev.us.ml.com/forwarders/v621/ | grep Linux-x86_64 | awk -F'>' '{print $2}'|awk -F'.gz' '{print $1}'")
        end
end
Comment 2 Martin Magr 2015-10-22 14:02:26 UTC 
I was not able to find neither prodtarball nor labtarball fact implementation in any Puppet module we ship. Neither in Puppet or Facter such facts exist, so that has to be customer specific facts probably. 

Debugging output can be implemented either in facts themselves or in Puppet itself. There is nothing we can do on Puppet module level unfortunately.