[SERVER-2244] [Puppet Agent] Agent cannot resolve ssldir correctly Created: 2018/07/05  Updated: 2018/07/17

Status: Needs Information
Project: Puppet Server
Component/s: Puppet Server
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Gabor Garami Assignee: Gabor Garami
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template: PUP Bug Template
Method Found: Needs Assessment
QA Risk Assessment: Needs Assessment


My problem is very similar to this issue, however my problem does not go away when I delete /var/lib/puppet/ssl directory.

So, I have a Puppet Master that is also configured as its agent. Since I prefer a bit different directory structure that currently Puppet uses (I prefer the previous convention), I overridden some paths in the config:


logdir = /var/log/puppet
vardir = /var/lib/puppet
ssldir = /var/lib/puppet/ssl
rundir = /var/run/puppet
factpath = $vardir/lib/facter
confdir = /etc/puppet
codedir = /etc/puppet
server = central.int.example.com
daemonize = false
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
dns_alt_names = puppet,puppet.szervernet.hu


When I start agent, it does not pick up the overridden ssldir, nor the server directive under its own section.


root@central:/etc/puppet# puppet agent --configprint ssldir

I deleted /var/lib/puppet/ssl twice in a row and did not helped. But regardless of this, I think agent have to pick up overridden settings. Even if it's not follows any standards. If master can use these settings, agent have to do so.

Comment by Justin Stoller [ 2018/07/06 ]

confdir and vardir are special and are set before any other settings are resolved (they're needed to know where to read the config file you're setting them in for instance). If you must set vardir or confdir then you should do it from the cli when you invoke puppet, ie puppet agent --confdir /etc/puppet --vardir /var/lib/puppet It should then read the puppet.conf at /etc/puppet/puppet.conf and apply the settings normally.

Comment by Justin Stoller [ 2018/07/17 ]

Let me know the current state of things Gabor Garami

Generated at Fri Aug 07 08:37:54 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.