I am getting quite a weird trouble here with my puppet configuration.
On client and server (debian-squeeze), same version of puppet, clock synchronized.
Things were going great until I decided to install puppet-dashboard, I don't know at which step this lead to a failure, but here are the symptoms:
I have no certificate between the client and the server; I create on on client side which I send to server through this command:
puppetd --test --waitforcert 50
on the server side:
root@puppet:/var/lib/puppet/ssl# puppetca --list --all dev.goeland.lan (53:C8:AE:21:F0:64:FC:B8:7C:AD:7F:7A:1C:80:B0:4C) root@puppet:/var/lib/puppet/ssl# puppetca -s dev.goeland.lan notice: Signed certificate request for dev.goeland.lan notice: Removing file Puppet::SSL::CertificateRequest dev.goeland.lan at '/var/lib/puppet/ssl/ca/requests/dev.goeland.lan.pem' root@puppet:/var/lib/puppet/ssl# puppetca --list --all + dev.goeland.lan (FC:1A:E5:1F:D7:A3:C4:4A:B6:1A:7F:C6:4A:6E:07:55) root@puppet:/var/lib/puppet/ssl#
First, I don't understand why the fingerprint changes : before being signed, the certificate is like *:4C, and it turns into *.55. Maybe this is a correct behavior?
Then, from client:
root@dev:/var/lib/puppet/ssl# puppetd --test warning: peer certificate won't be verified in this SSL session info: Caching certificate for dev.goeland.lan err: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run root@dev:/var/lib/puppet/ssl#
Client refuses server certificate, while it has just been signed a the previous step!
Can anyone help me on this one?
Thanks a lot!