[Puppet Users] Re: Could not find class defined for specific environment when running puppet agent

2017-02-22 Thread John Gelnaw
I would ignore everything past "Using cached catalog from environment 'ops'" in your debugging, as it's cached and therefore probably represents a previous state of the puppet master catalog. Especially for testing, you can replace your puppet run with: service puppet stop && puppet agent --te

Re: [Puppet Users] Could not find class defined for specific environment when running puppet agent

2017-02-22 Thread Carthik Sharma
Hi, On Wed, Feb 22, 2017 at 8:22 AM, Jamals wrote: > Hi all, > > I have a curious problem that I'd appreciate help/guidance on. > > We are running puppetserver 2.6.0 (puppetmaster.domain.ca) with cobbler > 2.6.11 as our ENC. All our servers/nodes are centos 7.3 > > On the puppet client (node.do

Re: [Puppet Users] [PuppetDB] records not being expired from puppetdb?

2017-02-22 Thread Christopher Wood
Well that was daft of me, and you're exactly right. After applying this tuning older things are purged as expected. Thank you! On Wed, Feb 22, 2017 at 01:26:45PM -0800, Wyatt Alt wrote: > Hey Christopher, > > This is the default behavior of PuppetDB -- my guess is you can address it > by tuning

Re: [Puppet Users] [PuppetDB] records not being expired from puppetdb?

2017-02-22 Thread Wyatt Alt
Hey Christopher, This is the default behavior of PuppetDB -- my guess is you can address it by tuning your node-ttl and node-purge-ttl parameters, which are described here: https://docs.puppet.com/puppetdb/latest/configure.html#node-ttl PuppetDB won't expire or delete node data unless those

[Puppet Users] could not retrieve information from sources defined in new environment

2017-02-22 Thread Jamals
Hi all, I have a curious problem that I'd appreciate help/guidance on. We are running puppetserver 2.6.0 (puppetmaster.domain.ca) with cobbler 2.6.11 as our ENC. All our servers/nodes are centos 7.3 On the puppet client (node.domain.ca) when running the puppet agent we receive the following ou

[Puppet Users] Module Dependency Best Practices

2017-02-22 Thread Lesley Kimmel
All; I'm semi-new to Puppet and after having tried a couple different things I've developed some questions. I've read some articles that state making a module as self-contained as possible is a good practice. However, as I've tried to do that in a site with a large number of potential modules i

[Puppet Users] Could not find class defined for specific environment when running puppet agent

2017-02-22 Thread Jamals
Hi all, I have a curious problem that I'd appreciate help/guidance on. We are running puppetserver 2.6.0 (puppetmaster.domain.ca) with cobbler 2.6.11 as our ENC. All our servers/nodes are centos 7.3 On the puppet client (node.domain.ca) when running the puppet agent we receive the following ou

Re: [Puppet Users] syntax issue over puppet_4

2017-02-22 Thread Ren
yeah you absolutely right ! thank you. now it works. am still discovering puppet. Le mercredi 22 février 2017 15:29:54 UTC+1, Dirk Heinrichs a écrit : > > Am 22.02.2017 um 14:28 schrieb Ren: > > *Error: Failed to apply catalog: Could not find dependency > Package[openssh-server] for File[/etc

Re: [Puppet Users] syntax issue over puppet_4

2017-02-22 Thread Dirk Heinrichs
Am 22.02.2017 um 14:28 schrieb Ren: > *Error: Failed to apply catalog: Could not find dependency > Package[openssh-server] for File[/etc/ssh/sshd_config] at > modules/sshd/manifests/init.pp:14* It's not declared (package {$ssh_pkg: ...}). Wondering why it worked in P3... Bye... Dirk -- *

[Puppet Users] syntax issue over puppet_4

2017-02-22 Thread Ren
Hi all, I'm hoping you can point out some detail I'm missing. Puppet agent seems to fail with manifest working fine with puppet3 but not for puppet4. Thank you . *Error: Failed to apply catalog: Could not find dependency Package[openssh-server] for File[/etc/ssh/sshd_config] at modules/ssh