Re: [Puppet Users] Re: Way to pass "arguments" into a subclass?

Quoting jcbollinger on Mon, May 02 09:28: > > > Then in nodes/%{::trusted.certname}.yaml for any host that needs to > > override the default in ucdpuppet::kerberos::params, I put: > > > > ucdpuppet::kerberos::params::krb5_source: "krb5.conf.special" > > > > > > No

Re: [Puppet Users] PE missing referents for production modules

On Tuesday, May 3, 2016 at 10:02:30 AM UTC-4, Lindsey Smith wrote: > > > > On Mon, May 2, 2016 at 1:54 PM, Matthew Pounsett > wrote: > >> >> I'm setting up a test deployment of the latest PE. I haven't run PE for >> a couple of years, and it looks like a few

Re: [Puppet Users] Re: lvm_support.rb file fails to load correctly with an execution expired warning in the logs

Hi John, the logging would suggest that there is no hanging while loading the LVM facts. All the facts appear to load. Obviously, as we are not using the most recent puppetlabs-lvm module, we don't have the component relating to lvm_vg_#*name*_pvs as you highlight above. Regarding lvm version and

Re: [Puppet Users] PE missing referents for production modules

On Mon, May 2, 2016 at 1:54 PM, Matthew Pounsett < matthew.pouns...@rightside.co> wrote: > > I'm setting up a test deployment of the latest PE. I haven't run PE for a > couple of years, and it looks like a few (perhaps a lot of) things have > changed. > > I have a completely fresh install of >

[Puppet Users] Re: lvm_support.rb file fails to load correctly with an execution expired warning in the logs

On Tuesday, May 3, 2016 at 5:57:43 AM UTC-5, karl@ammeon.com wrote: > > Just to add some context: > > puppet --version ==> 3.3.2 > facter --version ==> 1.6.18 > ruby --version ==> ruby 1.8.7 (2013-06-27 patchlevel 374) [x86_64-linux] > uname -a ==> Linux ms1 2.6.32-504.el6.x86_64 #1 SMP Tue

[Puppet Users] Re: Erb template

On Monday, May 2, 2016 at 11:29:51 AM UTC-5, Manoj Muraleedharan wrote: > > I have two erb template, one for main config file and another for child > process config file. I need to want to create config file for 3 child > process config file inside main erb template by calling another erb >

Re: [Puppet Users] Foreman integration with Puppet v4!

No is a bit too fast of an answer. The reality is somewhat like the facebook relationship status "it's complicated". The installer doesn't support puppet 4 at the moment, so you'll have to run from source. That said, we have foreman 1.10 and 1.11 running mostly fine from source with puppet

Re: [Puppet Users] PE missing referents for production modules

Doesthe module show up with 'puppet module list'? You may need to add '--environment=production' and/or '--modulepath=/etc/puppetlabs/code/environments/production/modules'. Rob Nelson rnels...@gmail.com On Mon, May 2, 2016 at 4:54 PM, Matthew Pounsett < matthew.pouns...@rightside.co> wrote: >

[Puppet Users] Re: lvm_support.rb file fails to load correctly with an execution expired warning in the logs

Just to add some context: puppet --version ==> 3.3.2 facter --version ==> 1.6.18 ruby --version ==> ruby 1.8.7 (2013-06-27 patchlevel 374) [x86_64-linux] uname -a ==> Linux ms1 2.6.32-504.el6.x86_64 #1 SMP Tue Sep 16 01:56:35 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux On Tuesday, 3 May 2016

[Puppet Users] PE missing referents for production modules

I'm setting up a test deployment of the latest PE. I haven't run PE for a couple of years, and it looks like a few (perhaps a lot of) things have changed. I have a completely fresh install of puppet-enterprise-2016.1.1-el-7-x86_64 on Centos 7. I've added a module as

[Puppet Users] lvm_support.rb file fails to load correctly with an execution expired warning in the logs

Hi all, We are seeing the following "execution expired" warning in the logs intermittently during a puppet cycle: *Apr 25 19:06:53 Node1 puppet-agent[20513]: Could not load fact file /var/lib/puppet/lib/facter/lvm_support.rb: execution expired*On further investigation and with some logging

Re: [Puppet Users] Foreman integration with Puppet v4!

hi, Vishvendra Singh Chauhan schrieb am Di., 3. Mai 2016 um 11:08 Uhr: > Dear All, > > > Is there any way to integrate foreman with puppet v4? > > No. Here can you watch the state of the work process: http://projects.theforeman.org/issues/8447 Greetings, Björn -- You

[Puppet Users] Foreman integration with Puppet v4!

Dear All, Is there any way to integrate foreman with puppet v4? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To

Re: [Puppet Users] Erb template

I can't see how this would work at all, given that templates are filled out by the Puppet master and sent to the client. Even if you used "pure Ruby" inside the ERB to process another ERB file, the Puppet master would have no way to know that it's supposed to pick up that other file and

Re: [Puppet Users] Erb template

It is probably better two generate the child*.conf from your puppet code rather than having an erb template generate another file (I am not even sure that works). What version of puppet are you running and could you show us some code? -- Lowe Schmidt | +46 723 867 157 On 2 May 2016 at 15:53,