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
(http://reductivela
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 sh
Thanks I manage to do it...
On Tue, Nov 10, 2009 at 2:26 PM, ew 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 statement:
>
> clas
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,
> 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: http://pro
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
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 ma
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
On 11/11/09 18:23, Larry Ludwig wrote:
>
>
>>> 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:/
> > 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
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 corre
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
puppetd.conf
On 11/11/09 16:47, Larry Ludwig wrote:
>
>
>
> On Nov 11, 10:30 am, Brice Figureau
> wrote:
>> 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-
On Nov 10, 10:13 am, Thomas Bellman wrote:
> The problem is that 'chkconfig 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 a 'chkconfig --del ',
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
Ticket opened: http://projects.reductivelabs.com/issues/2803
-L
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe
On Nov 11, 10:30 am, Brice Figureau
wrote:
> 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 t
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 Nov 10, 8:38 am, Arnau Bria wrote:
> I've been
> readinghttp://reductivelabs.com/trac/puppet/wiki/TypeReference#serviceand I
> did not find out how to manage a service that only enables a cron:
>
> like:
>
> # /etc/init.d/pakiti status
> nightly pakiti update is disabled
>
> # /etc/init.d/y
> The code is completely different between 0.24.8 and 0.25.1 which is why
> you're seeing a difference.
I understand this, but what works with 0.24.8 should work with 0.25.1
no? Hence it's looking more like a bug.
>
> Is network-config a module?
> If yes, then your source url is not correct, al
> I don't think you need to see it. Take a look at this... This might
> actually be a redhat bug.
For what it's worth, this all works great in sles (at least sles 11 -
haven't checked elsewhere):
uldbdb204e:/etc/rc.d # chkconfig snmpd
snmpd on
uldbdb204e:/etc/rc.d # find . -name '*snmpd*'
./rc3
On 11/11/09 04:26, Larry Ludwig wrote:
>
> Nope not it.
>
> Correct info:
>
> Nov 10 22:22:38 archive puppetmasterd[19932]: Not authorized to call
> find on /file_metadata/network-config/hosts/nsswitch.devcentos5.conf
> request.node: devcentos5.empoweringmedia.net request.ip: 192.168.10.41
>
>
>
22 matches
Mail list logo
