The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #11433

b64_zlib_yaml issue with RHEL4

Added by Corey Osman over 2 years ago. Updated over 2 years ago.

Status:ClosedStart date:12/15/2011
Priority:NormalDue date:
Assignee:Nigel Kersten% Done:

0%

Category:-
Target version:-
Affected Puppet version: Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

I continue to get this error with the 2.6 and 2.7 branches on RHEL4 (OS installed Ruby 1.8.1)

version 2.6.12 had the same issue so I can only run 2.6.9 which doesn’t have the security fix.

I do not know if 2.6.10 introduced the issue but 2.6.9 works great. This error causes puppet to not run.

Dec 15 20:22:33 puppet-agent[15870]: Starting Puppet client version 2.6.13 Dec 15 20:22:37 puppet-agent[15870]: Could not run Puppet configuration client: Could not render to b64_zlib_yaml: uninitialized constant Base64

Dec 15 20:21:19 puppet-agent[15490]: Starting Puppet client version 2.7.9 Dec 15 20:21:19 puppet-agent[15490]: Got an uncaught exception of type NoMethodError: undefined method `ascend' for #<Pathname:/var/lib/puppet> Dec 15 20:21:24 puppet-agent[15490]: Could not run Puppet configuration client: Could not render to b64_zlib_yaml: uninitialized constant Base64

History

#1 Updated by Michael Stahnke over 2 years ago

  • Status changed from Unreviewed to Needs Decision

As a small bit perhaps helpful advice, if your master is running something post 2.6.12 or 2.7.6, and you’ve got a new certificate on the 2.6.x client, you are not vulnerable to the security subject-alt-name certificate issue.

#2 Updated by Michael Stahnke over 2 years ago

  • Assignee set to Nigel Kersten

Nigel, here is another 1.8.1 bug.

Corey, RHEL4 goes end of life Feb 28, 2012. If we get a fix in, it wouldn’t be released until the January or February release of Puppet at this point. The fix would also only go into the 2.7 series as the 2.6 series is closed except for security patches.

#3 Updated by Michael Stahnke over 2 years ago

  • Status changed from Needs Decision to Closed

I’m sorry, but we’re not going to be able to fix this.

If you’re going to stay on EL4, I’d recomend either installing the RHEL5 ruby stack on it, (thus getting 1.8.5) or using Puppet Enterprise which includes it’s own ruby (1.8.7). Other options may include Ruby Enterprise Edition.

Also available in: Atom PDF