Hi Larry,
I re-read the whole thread, and I might have been wrong.
Your module files are indeed placed in network-config/files, correct?
Based on the error message (which mentions network-config/hosts) I
thought you placed your files at the wrong place. My bad.
On 11/11/09 15:52, Larry Ludwig
On Wed, 11 Nov 2009 07:17:05 -0800 (PST)
jcbollinger jcbollinger wrote:
Hi John,
If your initscript supports a status argument (as RedHat-provided ones
do) then you can instruct Puppet to use it by setting
hasstatus = true
on your Service resource(s).
That's what I understood and I
On Nov 10, 10:13 am, Thomas Bellman bell...@nsc.liu.se wrote:
The problem is that 'chkconfig service on' does an implicit add of
the service; but it does a half-assed job, in that it only adds the
start links, not the kill links. Thus, it is very easy to get into
the broken state by doing
In case anybody else has found their --noop flag (and probably others)
ignored with 24.6 here's why, and while this may be a known issue I
didn't find it in the discussion board after some searching so wanted
to save others..
I can't remember why it was done, but at some point I made
Hi,
Could it be that one of your environment doesn't have network-config?
Yes they do not. The 'development' env has newer code.
Could it be that in 0.25 the client is in this environment instead of
being in the one you think it is in?
Checked LDAP config and it is in fact in the correct
BTW, how do you tell the client to be in a particular environment?
There is currently a bug report about this (ie environment can only be
set on the client and not in external_nodes anymore).
Which ticket # is it? Is it this one?
http://projects.reductivelabs.com/issues/2748
having the
On 11/11/09 18:14, Larry Ludwig wrote:
Hi,
Could it be that one of your environment doesn't have network-config?
Yes they do not. The 'development' env has newer code.
Then that's your issue, because of #2748.
Could it be that in 0.25 the client is in this environment instead of
being
jcbollinger wrote:
Following the principle of exercising only documented behavior, I
think Puppet's redhat service provider should recognize only those
services reported by chkconfig --list. That would prevent Puppet from
causing a misconfiguration by turning on a service not already managed
Ugh, now I'm getting another error with Puppet. The above node now
works, but deploying it on another node I get this error:
Could not retrieve catalog from remote server: Could not intern from
pson: Could not convert from pson: Could not find relationship target
''
I have set the environment
Ugh, now I'm getting another error with Puppet. The above node now
works, but deploying it on another node I get this error:
Could not retrieve catalog from remote server: Could not intern from
pson: Could not convert from pson: Could not find relationship target
''
yes:
Hi,
I'm trying to create an authorized key and a user in one go and I'm
not getting anywhere:
class users {
user { ben :
ensure = present,
uid = 1010,
gid = users,
managehome = true,
password = blahblah
}
ssh_authorized_key { ben-key:
ensure = present,
key=
Thanks I manage to do it...
On Tue, Nov 10, 2009 at 2:26 PM, ew erhard.w...@gmail.com wrote:
hi
puppet provides the following function to maintain authorized_key
files:
http://reductivelabs.com/trac/puppet/wiki/TypeReference#ssh-authorized-key
we mange our keys with the following
On Nov 10, 2009, at 1:16 PM, James Turnbull wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Nasrat wrote:
I'd like to make sure there is still a low cost of entry to getting
patches in - so it should be possible to insert a simple pointer in a
ticket to the CLA, it should also
So I'm trying to get multiple environments to work with puppet 0.25.1
on ubuntu 8.04 and no matter what I do, puppet just completely ignores
any environment setting. There's really next to no information in
terms of configuration on the multiple environments documentation page
14 matches
Mail list logo
