OlliesDad@googlemail.com
2012-Feb-24 10:12 UTC
[Puppet Users] RHEL4 + 2.6.11 and Puppet CA/Master at 2.7.9
Hello, As the 2.7 branch doesn''t seem to be available for RHEL4 (yes I know EOS next week) am trying to use a 2.6.11 client for our new Puppet infrastructure to replace the creaking one we have now. The POC setup is all running behind an F5 with a pair of CA''s and seperate pool of Puppet Masters. RHEL5/6 clients running 2.7.9 work fine. The older version on RHEL4 gives me SSL issues "does not match" etc. Full clean out tried as per usual but nothing works. Are these compatible. Or any known issues/workarounds. Google hasn''t helped. Thanks Paul -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
OlliesDad@googlemail.com
2012-Feb-24 15:44 UTC
[Puppet Users] Re: RHEL4 + 2.6.11 and Puppet CA/Master at 2.7.9
This actually comes back with:- info: Creating a new SSL key for <host> warning: peer certificate won''t be verified in this SSL session. info: Caching certificate for ca warning: peer certificate won''t be verified in this SSL session. warning: peer certificate won''t be verified in this SSL session. info: Creating a new SSL certificate request for <host> info: Certificate Request fingerprint (md5): BB:92:3E:98:C7:2C:9C: 18:42:A4:38:E2:C2:34:F1:3D warning: peer certificate won''t be verified in this SSL session. err: Could not request certificate: Could not intern from yaml: dump format error Exiting; failed to retrieve certificate and waitforcert is disabled The YAML from the ENC looks like this:- --- parameters: ext_dev: "true" classes: - auth - autofs - bootloader - crashdump - cron - disks - email - galaxy - ganglia - hardwaremon - hpbios - identification - kernelparams - locale - lom - network - nimbus - ntp - packages - profile - puppetclient - resolver - security - selinux - services - ssh - sudo - syslog - systemusers - tsgtools - verify - vmware environment: engineering Is there anything wrong the 2.7.9 clients work fine ? Thanks Paul On Feb 24, 10:12 am, "Ollies...@googlemail.com" <Paul.Seym...@barcap.com> wrote:> Hello, > > As the 2.7 branch doesn''t seem to be available for RHEL4 (yes I know > EOS next week) am trying to use a 2.6.11 client for our new Puppet > infrastructure to replace the creaking one we have now. > > The POC setup is all running behind an F5 with a pair of CA''s and > seperate pool of Puppet Masters. > > RHEL5/6 clients running 2.7.9 work fine. The older version on RHEL4 > gives me SSL issues "does not match" etc. Full clean out tried as per > usual but nothing works. > > Are these compatible. Or any known issues/workarounds. Google hasn''t > helped. > > Thanks > Paul-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.