Re: [Puppet Users] ssl signing issue

Hi Chris, On 30 Jun 2014, at 05:23, Chris wrote: > > master gets it: > # puppet ca list > client (SHA256) > D4:6D:33:FE:33:98:C1:42:77:ED:D3:33:16:8D:A0:C6:37:1F:90:6B:03:D2:EC:79:52:FF:03:2E:8C:7F:D8:50 > > and has signed itself: > # puppet ca list --all > client (SHA256) > D4:6D:

[Puppet Users] ssl signing issue

Hi, I'm trying to get signing right and have come up with a weird situation. Both master and client are running 3.6.2 (rpms from puppetlabs). client config: [main] vardir = /var/lib/puppet logdir = /var/log/puppet rundir = /var/run/puppet ssldir = /var/lib/puppet/ssl classf

Re: [Puppet Users] Community packages : error: rubygem-stomp-1.3.2-1.el5

Hi, I confirm, the new package works well, thank you for the quick response ! Dje Le 27/06/2014 19:32, Melissa Stone a écrit : Hi Dje, This should be fixed now. Thank you for letting us know about this issue. On Thu, Jun 26, 2014 at 9:10 PM, Moses Mendoza > wro

[Puppet Users] Re: puppetdb, puppet master, puppet agent and facter compatibility

Ok your route is the wrong way around , puppetdb wont play nice with sub 3.5.1 in my experience so your puppet master should be upgraded first when it is upgraded then do the rest, and why not version pin your clients via a puppet class ? My experience is that the 2.x client will give you troub

[Puppet Users] puppetdb, puppet master, puppet agent and facter compatibility

Hi all, I have an installation with puppetdb 1.6.3, puppet master 3.4.3, agents ranging from 2.7 to 3.4 and various facter versions, up to 2.X Now I'm evaluating to upgrade this installation starting from puppetdb and then down the pipe, but even looking at documentation I'm not sure about the