Project

General

Profile

Bug #2097

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

Added by Dominic Cleal over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Puppet integration
Target version:
Difficulty:
easy
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

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.

Associated revisions

Revision 2a1269eb (diff)
Added by Dominic Cleal over 9 years ago

fixes #2097 - improve debug when `puppet master --configprint` fails

Revision 96cefa08 (diff)
Added by Dominic Cleal over 9 years ago

refs #2097 - update test to include stderr redirect

History

#1 Updated by Dominic Cleal over 9 years ago

  • Category changed from Puppet Reports to Puppet integration
  • Status changed from Assigned to Ready For Testing

#2 Updated by Dominic Cleal over 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF