Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
"distdescription"=>"Debian GNU/Linux 7.7 (wheezy)"
puppetserver version: 0.3.0-1puppetlabs1
Description
There's a discrepancy between what --configprint (and the config file) shows and where puppet is looking for certificate requests.
sheela@rugnor:~$ sudo puppet agent -t
Info: csr_attributes file loading from /etc/puppet/csr_attributes.yaml
Info: Creating a new SSL certificate request for instance1
Info: Certificate Request fingerprint (SHA256): 10:2E:B9:74:92:0D:A5:FC:74:AB:E0:78:CC:06:29:F2:9D:29:D2:08:B8:0C:6B:0F:B8:C9:49:C5:D4:B1:D6:43
Error: Could not request certificate: Error 500 on SERVER: <html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 500 </title>
</head>
<body>
<h2>HTTP ERROR: 500</h2>
<p>Problem accessing /production/certificate_request/instance1. Reason:
<pre> /var/lib/puppet/ssl/ca/requests/instance1.pem (No such file or directory)</pre></p>
<hr /><i><small>Powered by Jetty://</small></i>
</body>
</html>
Exiting; failed to retrieve certificate and waitforcert is disabled
This what configprint shows
sheela@rugnor:~$ sudo puppet agent --configprint ssldir
/etc/puppet/ssl
This is the /etc/puppet/puppet.conf
[main]
logdir = /var/log/puppet
ssldir = /etc/puppet/ssl
rundir = /var/run/puppet
pluginsync = true
parser = future
[agent]
report = true
certname = instance1
