Project

General

Profile

Actions
Copy link

Bug #1914

closed

Proxy should throw an error when loading a nonexistant puppet.conf

Added by Greg Sutcliffe over 11 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Greg Sutcliffe
Category:
Puppet
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

This just came up as a user upgraded from 0.4.2 to 1.0.1 - no :puppet_conf: setting in proxy/settings.yml. So the proxy tried to load ~foreman-proxy/.puppet/puppet.conf which doesn't exist. Instead of failing, it simply produced the default environments (["production"]). This made it rather difficult to troubleshoot.

The proxy should exit with an error if :puppet: true and the puppet.conf cannot be found. It should also print the file it does load (when successful) to the logs.

Actions
Copy link
 #1

Updated by Anonymous over 11 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF