Project

General

Profile

Actions
Copy link

Bug #2097

closed

Improve debug when unable to get Puppet settings with bad return code

Added by Dominic Cleal almost 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Dominic Cleal
Category:
Puppet integration
Target version:
1.1
Difficulty:
easy
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Currently PuppetSetting raises an exception when the return code of the puppet master --configprint command is bad. This is usually down to configuration, but there's not enough debug to help.

It currently raises this message:

unable to get [:hostcert, :localcacert, :hostprivkey, :storeconfigs] Puppet setting: <stdout>

It should also provide the path to puppetmasterd it ran (as people have had $PATH issues), the full command (to include the puppet.conf location) and stderr.

Actions
Copy link

Also available in: Atom PDF