Ask Your Question
1

Does puppet work at all on Fedora 17

asked 2012-06-01 11:35:20 -0500

Clayton Louden gravatar image

Hi,

I've tried to migrate my Fedora 16 puppet master and a couple of clients to Fedora 17 and puppet 2.7 (ruby 1.9) but I keep hitting this error:

err: Could not request certificate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed. This is often because the time is out of sync on the server or client

I was just wondering: Has anyone out there managed to get puppet to work under Fedora 17? It seems that the package maintainers are well aware of some puppet 2.6 <-> 2.7 incompatibilities an some puppet 2.6 and ruby 1.9 issues, but did anyone really test if you can connect a Fedora 17 puppet 2.7 client to a Fedora 17 puppet 2.7 master? I've fiddled hours but wasn't able to manage that.

edit retag flag offensive close merge delete

5 Answers

Sort by ยป oldest newest most voted
0

answered 2012-06-04 06:12:41 -0500

misc gravatar image

That's a very generic problem, I found this http://urgetopunt.com/puppet/2011/09/14/puppet-ruby19.html that could help you, you just need to do a symlink.

edit flag offensive delete link more
0

answered 2012-06-13 06:07:31 -0500

PDubois gravatar image

I've had the same frustrating issue. Looks like Puppet will have this fixed in '2.7.15'. Ruby changed the default SSL certificate handling to 'verify peer' and this has caused puppet's initial connection to the puppetmaster to break.

http://projects.puppetlabs.com/issues/14795

edit flag offensive delete link more
0

answered 2012-06-03 16:15:53 -0500

I only have one fedora 17 machine so I installed puppet-server and puppet on the same machine. Running puppet without problems.

edit flag offensive delete link more
0

answered 2012-06-13 06:16:23 -0500

PDubois gravatar image

http://projects.puppetlabs.com/projects/1/wiki/Release_Notes

If I read this properly, the puppet release 2.7.16 will fix this, 2.7.15 seems like it won't be released.

So, question is : when will we be seeing that update find it's way into F17?

edit flag offensive delete link more
0

answered 2012-06-13 06:08:01 -0500

PDubois gravatar image

I've had the same frustrating issue. Looks like Puppet will have this fixed in '2.7.15'. Ruby changed the default SSL certificate handling to 'verify peer' and this has caused puppet's initial connection to the puppetmaster to break.

http://projects.puppetlabs.com/issues/14795

edit flag offensive delete link more

Question Tools

2 followers

Stats

Asked: 2012-06-01 11:35:20 -0500

Seen: 992 times

Last updated: Jun 13 '12