@Carthik and @John, thank you both for your input. I finally got this to
work earlier in the week but did not have a chance to post.
Here's what I changed on puppetmaster's
`/etc/puppetlabs/puppet/puppet.conf` :
[main]
environmentpath = /etc/puppetlabs/code/environments
node_terminus = exec
ext
Thank you so much for your response.
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.
>
I had gone ahead and registered the client cert with puppetm
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
Figured this out.. It was a mis-spelling in the nodes.pp file. But it
was also an error in the file class file it's self. I had some single
quotes around the username and group that shouldh't haven't been there..
Incredibly stupid.. :/
On Sunday, September 28, 2014 4:31:41 PM UTC-5, omfg9
I forgot to add this..
warning: Could not find class webapps::apps_sever_content for
i-xx.ec2.internal
Could not find class webapps::apps_sever_content at
/var/els/puppet/manifests/nodes.pp:10 on node i-xx.ec2.internal
On Sunday, September 28, 2014 4:31:41 PM UTC-5, omfg9899 wrote:
>
>
On Tuesday, May 6, 2014 5:44:39 AM UTC-5, devaki prabhu wrote:
>
> Hi everybody,
>
> i have to install keystone package on puppet client :
> i have some module in puppet master
> /etc/puppet/modules/keystone/manifests/init.pp
> and when i include it in client ,getting an class not found.
> any
Hi everybody,
i have to install keystone package on puppet client :
i have some module in puppet master
/etc/puppet/modules/keystone/manifests/init.pp
and when i include it in client ,getting an class not found.
any help is accepted.
Thank you.
Thank you very much!
It's working now.
Indeed when I have some spare time I may attempt to write another
module.
Dmytro
On Dec 16, 9:39 pm, "luke.bigum" wrote:
> Dmytro,
>
> I'm a git noob :) I've had a look at the module now. I wouldn't say
> it's designed that well and I think a few people on
Dmytro,
I'm a git noob :) I've had a look at the module now. I wouldn't say
it's designed that well and I think a few people on this list would
agree.
To fix your problem I think you'll have to "include rsync" first,
which will then import "classes/*.pp", which will then allow Puppet to
find the
That github link doesn't work for me so don't know the internals of
this module, but if the module is called "rsync", as indicated by this
module path: /etc/puppet/modules/rsync/, then any sub classes of that
should be in the rsync namespace... Are you sure it's not supposed to
be rsync::rsyncd?
A
Just to be sure we're on the same page. It doesn't work like this?
init.pp::
import "*"
class rhnsd {
}
Is the module path in puppet set to your module path? Other than this I
can't spot any other errors. Also make sure you have restarted
puppetmasterd, in many cases when developing puppet code
Hm, I thought that puppet would search for filname X in module Y
manifestdir when you included a class like include "Y::X", guess I'm
wrong there.
On the other hand, adding the import statement in the beginning of
rhnsd/manifests/init.pp yeilds the same error.
On 17 Jun, 13:10, Silviu Paragina w
12 matches
Mail list logo
