The Puppet Labs Issue Tracker has Moved:

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using See the following page for information on filing tickets with JIRA:

Bug #14793

Puppet registration with master ruby 1.9.3

Added by Maurice James almost 4 years ago. Updated almost 4 years ago.

Status:AcceptedStart date:06/03/2012
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Affected Puppet version:2.7.13 Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:


Unable to successfully register new agents running Fedora17 with ruby 1.9.3. I have tried the work around from, but the issue remains. The error is:

[root@host certs]# puppetd agent —server hostname.domain —test /usr/share/rubygems/rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead. 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

System details: ruby 1.9.3p194 (2012-04-20 revision 35410) [i386-linux] 3.3.4-5.fc17.i686.PAE puppet-2.7.13-1.fc17.noarch

Related issues

Related to Puppet - Bug #8858: Ruby 1.9 defaults HTTPS connections to "peer verify" rath... Closed 06/03/2012


#1 Updated by Kelsey Hightower almost 4 years ago

  • Status changed from Unreviewed to Accepted

#2 Updated by John Florian almost 4 years ago

This is a duplicate of #9084.

Also available in: Atom PDF