[Puppet Users] Re: Purging unmanaged augeas entries?

[seph]

Frank Sweetser  writes:

> I'm in the process of setting up sudoers entries to get managed by
> augeas.

If you can insure a suitable recent sudo, you can use sudo's #includedir
option and just manage a directory.

seph

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Inherited Client and Server Apps

[Teyo Tyree]

Yeah,  I can update the external nodes page no problem.

On Mon, Dec 14, 2009 at 3:54 PM, James Turnbull  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Teyo
>
> If you have a chance do you want to throw your email and my email
> into the External nodes page?  It really needs some more explanation.
>
> Or I can if you're busy.
>
> Cheers
>
> James Turnbull
>
> - --
> Author of:
> * Pro Linux System Administration (http://tinyurl.com/linuxadmin)
> * Pulling Strings with Puppet (http://tinyurl.com/pupbook)
> * Pro Nagios 2.0 (http://tinyurl.com/pronagios)
> * Hardening Linux (http://tinyurl.com/hardeninglinux)
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.7 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEVAwUBSya0GyFa/lDkFHAyAQIh1wgAtu4EMAg83s4F0JOfA0VqzFvCbngs7I0F
> Hb9xrMooD5oOa8HJclfaUqMH9pcD4w5Lv8zcF+w2KMWBDaNQTXMOaNeU/n2gPEzZ
> R6wc6dTxKmWbyShnWHE6v4OofiOFMQzHJ3ibIwJWyOguoWM46LH+ANYLauugFVmj
> eWhRG0oegiyzbD1eXaUxhDl7ZgCTUmr+OF5aaik+X3BOYkSY4tJVK5HAFU/O8vUS
> udaBQ1v/KFJRHQYmFbT1tDOgvaDEyM42BKYvqXt8YK7+2XBDLJqbXM7DTjsUvb1m
> heVjvBFbEK0cGtCbmrV7TX50ABbItV6jre4PKoiY1qltoQU+UEyK0w==
> =IMem
> -END PGP SIGNATURE-
>
> --
>
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>
>
>



-- 
Teyo Tyree :: www.reductivelabs.com :: +1.615.275.5066

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Configuring Networking

[Scott Smith]

Douglas Garstang wrote:
> b) How do you require a definition? That makes no sense.

A definition is essentially just a custom resource.

-scott

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Configuring Networking

[jcbollinger]

On Dec 15, 5:01 pm, Douglas Garstang  wrote:
> I'll trying to work out the best way to configure networking in
> puppet, being routes, dns and ip addresses.
>
> First question... are definitions executed in the order they appear?

Do not attempt to rely on file order to control the sequence in which
Puppet applies resources to the client system.  Individual resources
should instead use the "require" and / or "before" parameters to
express dependencies on other resources or classes.

I note also that you need to already have at least a partially-
functional network configuration for Puppet to be able to retrieve its
catalog from a remote puppetmaster.  That makes for a bit of a chicken-
and-egg problem with using Puppet to set up networking.  It's not
insurmountable, and no doubt you've already thought about that, but I
just thought I'd mention it.

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Configuring Networking

[Douglas Garstang]

On Tue, Dec 15, 2009 at 3:59 PM, Steven VanDevender  wrote:
> Douglas Garstang writes:
>  > On Tue, Dec 15, 2009 at 3:47 PM, Peter Meier  
> wrote:
>  > > -BEGIN PGP SIGNED MESSAGE-
>  > > Hash: SHA1
>  > >
>  > >> First question... are definitions executed in the order they appear?
>  > >
>  > > puppet doesn't execute anything. it manages resources and defines are
>  > > resources as well.
>  >
>  > Fine. Does puppet manages resources and defines in the order they appear?
>
> Ordering is indeterminate unless "require" or "before" are used in
> resource definitions, which then produce the declared ordering
> relationship.

I was hoping that was just classes. Watching the logs seemed to
indicate that definitions were acted upon first.

Oh well, back to my original question. How can I make sure that my
network definitions are done FIRST? And before anyone says to use
require, I can't a) put require on every single damn resource in my
puppet config requiring the networking. That's asinine and b) How do
you require a definition? That makes no sense.

Doug.

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Configuring Networking

[Steven VanDevender]

Douglas Garstang writes:
 > On Tue, Dec 15, 2009 at 3:47 PM, Peter Meier  wrote:
 > > -BEGIN PGP SIGNED MESSAGE-
 > > Hash: SHA1
 > >
 > >> First question... are definitions executed in the order they appear?
 > >
 > > puppet doesn't execute anything. it manages resources and defines are
 > > resources as well.
 > 
 > Fine. Does puppet manages resources and defines in the order they appear?

Ordering is indeterminate unless "require" or "before" are used in
resource definitions, which then produce the declared ordering
relationship.

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Configuring Networking

[Scott Smith]

Douglas Garstang wrote:
> On Tue, Dec 15, 2009 at 3:47 PM, Peter Meier  wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>> First question... are definitions executed in the order they appear?
>> puppet doesn't execute anything. it manages resources and defines are
>> resources as well.
> 
> Fine. Does puppet manages resources and defines in the order they appear?
> 

No, it's declarative, not imperative.

http://en.wikipedia.org/wiki/Declarative_programming
http://en.wikipedia.org/wiki/Imperative_programming

-scott

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Configuring Networking

[Douglas Garstang]

On Tue, Dec 15, 2009 at 3:47 PM, Peter Meier  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>> First question... are definitions executed in the order they appear?
>
> puppet doesn't execute anything. it manages resources and defines are
> resources as well.

Fine. Does puppet manages resources and defines in the order they appear?

Doug.

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Configuring Networking

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

> First question... are definitions executed in the order they appear?

puppet doesn't execute anything. it manages resources and defines are
resources as well.

cheers pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAksoIAEACgkQbwltcAfKi3/t9wCeOrOj9JhiI1DfNugwI3DzxPOc
TqQAoIq6pL9fE3iyIQsgiwEdBYEn4G5Z
=By1d
-END PGP SIGNATURE-

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Configuring Networking

[Douglas Garstang]

On Tue, Dec 15, 2009 at 3:22 PM, Douglas Garstang
 wrote:
> On Tue, Dec 15, 2009 at 3:21 PM, Scott Smith  wrote:
>> Douglas Garstang wrote:
>>> On Tue, Dec 15, 2009 at 3:14 PM, Scott Smith  wrote:
 Douglas Garstang wrote:
> I'll trying to work out the best way to configure networking in
> puppet, being routes, dns and ip addresses.
>
 http://github.com/ohlol/puppet-network

 Doesn't handle route-#{iface} files, but would be trivial to add.

 -scott
>>>
>>> Thanks Scott, so you have some definitions to reconfigure networking,
>>> but how do you ensure that they run BEFORE everything else?
>>>
>>
>> You can use require =>
>
> Require in a definition, or in the classes? It doesn't seem feasible
> to me to put a require on every single object in my puppet config
> requiring networking!
>
> Doug
>

And... even then I'd be requiring a definition, not a class. Is that
even valid? How would the syntax look?

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Configuring Networking

[Douglas Garstang]

On Tue, Dec 15, 2009 at 3:21 PM, Scott Smith  wrote:
> Douglas Garstang wrote:
>> On Tue, Dec 15, 2009 at 3:14 PM, Scott Smith  wrote:
>>> Douglas Garstang wrote:
 I'll trying to work out the best way to configure networking in
 puppet, being routes, dns and ip addresses.

>>> http://github.com/ohlol/puppet-network
>>>
>>> Doesn't handle route-#{iface} files, but would be trivial to add.
>>>
>>> -scott
>>
>> Thanks Scott, so you have some definitions to reconfigure networking,
>> but how do you ensure that they run BEFORE everything else?
>>
>
> You can use require =>

Require in a definition, or in the classes? It doesn't seem feasible
to me to put a require on every single object in my puppet config
requiring networking!

Doug

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Announcing Puppet Dashboard 0.1.0 Release

[Rein Henrichs]

I understand and sympathize with the political/legal reasons. We obviously
want to do our best to support default RHEL4 configurations (since we have
so many RHEL4 nodes running Puppet) and it is unfortunate that the available
rake RPM lags JUST behind our requirements.

Try running things with a rake >= 0.8.3 dependency in config/environment.rb
and see if things break. There may be a simple way to fix it (by
monkey-patching rake inside our application, for instance) or it just might
work, which would be fantastic. I'll do some digging myself as well.

On Tue, Dec 15, 2009 at 3:00 PM, jw2dot...@gmail.com wrote:

> I'm sure this RubyGems topic probably deserves it's own thread...
>
> We go through a lot of political/legal paperwork at $WORK to deploy
> open-source software on our Red Hat systems.  Throwing logic aside, we
> managed to get approval to use any RPM package from EPEL, but that's
> not the case for RubyGems out on rubyforge.org.   RPM packages are
> simple to maintain and track for inventory purposes, but I agree with
> your comments on packaging systems falling behind..  (We still have
> lots of RHEL4 boxes, which can be very difficult with the ruby RPMs
> offered with that distro).
>
> Thanks for the gem docs.  I'll pursue that route.
>
>
> On Dec 15, 4:43 pm, Rein Henrichs  wrote:
> > At the risk of sparking another flame war, the best way to manage Ruby
> > library dependencies is via Rubygems rather than your platform's
> packaging
> > system -- which tends to have out of date Ruby packages and can conflict
> > with installed gems[1]. Fortunately, it is entirely possible and in fact
> > quite easy to install and use Rubygems as a local user (rather than
> > root)[2]. We've done our best to remove external dependencies but this
> one
> > unfortunately remains.
> >
> > The bottom line is that rake 0.8.4 is the first known-good version for
> the
> > version of Rails that Dashboard uses and, as such, the first that we
> > currently support. However, the rake install task (which is the only
> thing
> > that requires rake aside from running the spec suite) may work or be made
> to
> > work with older versions of rake. We would be happy to bump the
> dependency
> > down to 0.8.3 to provide out-of-the-box support for RHEL5 and will
> > gratefully accept patches that let us do that.
> >
> > [1] Seehttps://help.ubuntu.com/community/RubyOnRails
> > [2]http://docs.rubygems.org/read/chapter/3
> >
> > On Tue, Dec 15, 2009 at 1:09 PM, jw2dot...@gmail.com <
> jw2dot...@gmail.com>wrote:
> >
> >
> >
> > > Bummer.  Requires rake >= 0.8.4, but RHEL5/EPEL is only 0.8.3.
> >
> > >http://download.fedora.redhat.com/pub/epel/5/x86_64/repoview/rubygem-.
> ..
> >
> > > On Dec 14, 3:29 pm, Rein Henrichs  wrote:
> > > > Greetings Puppeteers,
> >
> > > > It's the holidays once again and, in the spirit of the season, I
> bring
> > > you
> > > > the immediate release of Puppet Dashboard 0.1.0, codenamed "Wira".
> > > Because
> > > > the Wira is a car. From Malaysia. And cars have dashboards. Even cars
> > > from
> > > > Malaysia.
> >
> > > > This release includes run success and total run time graphs and a
> global
> > > > status drop-down tab that provides at-a-glance system status updates.
> We
> > > are
> > > > still deciding on which information to present where and how best to
> > > present
> > > > it, so expect these to change in upcoming releases as we converge on
> the
> > > > most useful set of data to display. Coincidentally, this would be a
> great
> > > > time to tell us which information is most important to you on which
> > > pages.
> > > > You could even reply to this message on the list if you want (hint).
> >
> > > > Also, at the request of just about everyone, I've posted a tour of
> the
> > > > latest Dashboard release on the Reductive Labs blog athttp://
> > > reductivelabs.com/2009/12/14/a-tour-of-puppet-dashboard-0-1-0. Yes,
> > > > it includes screenshots. Huzzah.
> >
> > > > Get the code athttp://github.com/reductivelabs/puppet-dashboard.
> > > > Submit feature requests and bug reports athttp://
> > > projects.reductivelabs.com/projects/dashboard.
> >
> > > > Have a great holiday season, folks.
> >
> > > > --
> > > > Rein Henrichshttp://reductivelabs.com
> >
> > > --
> >
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Puppet Users" group.
> > > To post to this group, send email to puppet-us...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > puppet-users+unsubscr...@googlegroups.com
> 
> >
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/puppet-users?hl=en.
> >
> > --
> > Rein Henrichshttp://reductivelabs.com
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com
> .
> For more opt

Re: [Puppet Users] Configuring Networking

[Scott Smith]

Douglas Garstang wrote:
> On Tue, Dec 15, 2009 at 3:14 PM, Scott Smith  wrote:
>> Douglas Garstang wrote:
>>> I'll trying to work out the best way to configure networking in
>>> puppet, being routes, dns and ip addresses.
>>>
>> http://github.com/ohlol/puppet-network
>>
>> Doesn't handle route-#{iface} files, but would be trivial to add.
>>
>> -scott
> 
> Thanks Scott, so you have some definitions to reconfigure networking,
> but how do you ensure that they run BEFORE everything else?
> 

You can use require =>

-scott

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Configuring Networking

[Scott Smith]

Scott Smith wrote:
> http://github.com/ohlol/puppet-network
> 
> Doesn't handle route-#{iface} files, but would be trivial to add.
> 

Scratch that -- it does! :) Been a long time since I wrote that.

-scott

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Configuring Networking

[Douglas Garstang]

On Tue, Dec 15, 2009 at 3:14 PM, Scott Smith  wrote:
> Douglas Garstang wrote:
>> I'll trying to work out the best way to configure networking in
>> puppet, being routes, dns and ip addresses.
>>
>
> http://github.com/ohlol/puppet-network
>
> Doesn't handle route-#{iface} files, but would be trivial to add.
>
> -scott

Thanks Scott, so you have some definitions to reconfigure networking,
but how do you ensure that they run BEFORE everything else?

Doug.

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Configuring Networking

[Scott Smith]

Douglas Garstang wrote:
> I'll trying to work out the best way to configure networking in
> puppet, being routes, dns and ip addresses.
> 

http://github.com/ohlol/puppet-network

Doesn't handle route-#{iface} files, but would be trivial to add.

-scott

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Configuring Networking

[Douglas Garstang]

I'll trying to work out the best way to configure networking in
puppet, being routes, dns and ip addresses.

First question... are definitions executed in the order they appear?

If I put definitions way up the node hierarchy, and they are indeed
executed first, I can be sure that the network will be configured
first, which is what I want. However, I can't put IP addresses way up
the node hierarchy, as it doesn't make sense. So... where do I put
them?

Doug.

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Announcing Puppet Dashboard 0.1.0 Release

[jw2dot...@gmail.com]

I'm sure this RubyGems topic probably deserves it's own thread...

We go through a lot of political/legal paperwork at $WORK to deploy
open-source software on our Red Hat systems.  Throwing logic aside, we
managed to get approval to use any RPM package from EPEL, but that's
not the case for RubyGems out on rubyforge.org.   RPM packages are
simple to maintain and track for inventory purposes, but I agree with
your comments on packaging systems falling behind..  (We still have
lots of RHEL4 boxes, which can be very difficult with the ruby RPMs
offered with that distro).

Thanks for the gem docs.  I'll pursue that route.


On Dec 15, 4:43 pm, Rein Henrichs  wrote:
> At the risk of sparking another flame war, the best way to manage Ruby
> library dependencies is via Rubygems rather than your platform's packaging
> system -- which tends to have out of date Ruby packages and can conflict
> with installed gems[1]. Fortunately, it is entirely possible and in fact
> quite easy to install and use Rubygems as a local user (rather than
> root)[2]. We've done our best to remove external dependencies but this one
> unfortunately remains.
>
> The bottom line is that rake 0.8.4 is the first known-good version for the
> version of Rails that Dashboard uses and, as such, the first that we
> currently support. However, the rake install task (which is the only thing
> that requires rake aside from running the spec suite) may work or be made to
> work with older versions of rake. We would be happy to bump the dependency
> down to 0.8.3 to provide out-of-the-box support for RHEL5 and will
> gratefully accept patches that let us do that.
>
> [1] Seehttps://help.ubuntu.com/community/RubyOnRails
> [2]http://docs.rubygems.org/read/chapter/3
>
> On Tue, Dec 15, 2009 at 1:09 PM, jw2dot...@gmail.com 
> wrote:
>
>
>
> > Bummer.  Requires rake >= 0.8.4, but RHEL5/EPEL is only 0.8.3.
>
> >http://download.fedora.redhat.com/pub/epel/5/x86_64/repoview/rubygem-...
>
> > On Dec 14, 3:29 pm, Rein Henrichs  wrote:
> > > Greetings Puppeteers,
>
> > > It's the holidays once again and, in the spirit of the season, I bring
> > you
> > > the immediate release of Puppet Dashboard 0.1.0, codenamed "Wira".
> > Because
> > > the Wira is a car. From Malaysia. And cars have dashboards. Even cars
> > from
> > > Malaysia.
>
> > > This release includes run success and total run time graphs and a global
> > > status drop-down tab that provides at-a-glance system status updates. We
> > are
> > > still deciding on which information to present where and how best to
> > present
> > > it, so expect these to change in upcoming releases as we converge on the
> > > most useful set of data to display. Coincidentally, this would be a great
> > > time to tell us which information is most important to you on which
> > pages.
> > > You could even reply to this message on the list if you want (hint).
>
> > > Also, at the request of just about everyone, I've posted a tour of the
> > > latest Dashboard release on the Reductive Labs blog athttp://
> > reductivelabs.com/2009/12/14/a-tour-of-puppet-dashboard-0-1-0. Yes,
> > > it includes screenshots. Huzzah.
>
> > > Get the code athttp://github.com/reductivelabs/puppet-dashboard.
> > > Submit feature requests and bug reports athttp://
> > projects.reductivelabs.com/projects/dashboard.
>
> > > Have a great holiday season, folks.
>
> > > --
> > > Rein Henrichshttp://reductivelabs.com
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Puppet Users" group.
> > To post to this group, send email to puppet-us...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscr...@googlegroups.com
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/puppet-users?hl=en.
>
> --
> Rein Henrichshttp://reductivelabs.com

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Announcing Puppet dashboard 0.1.1 Release

[Rein Henrichs]

Greetings Folks,

Because I did something dumb, I am announcing the immediate release of
Puppet Dashboard 0.1.1. This release adds the missing reports migration that
made rake install totally not work.

My bad.

Get the code at http://github.com/reductivelabs/puppet-dashboard.
Submit feature requests and bug reports at
http://projects.reductivelabs.com/projects/dashboard.

-- 
Rein Henrichs
http://reductivelabs.com

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Announcing Puppet Dashboard 0.1.0 Release

[Rein Henrichs]

At the risk of sparking another flame war, the best way to manage Ruby
library dependencies is via Rubygems rather than your platform's packaging
system -- which tends to have out of date Ruby packages and can conflict
with installed gems[1]. Fortunately, it is entirely possible and in fact
quite easy to install and use Rubygems as a local user (rather than
root)[2]. We've done our best to remove external dependencies but this one
unfortunately remains.

The bottom line is that rake 0.8.4 is the first known-good version for the
version of Rails that Dashboard uses and, as such, the first that we
currently support. However, the rake install task (which is the only thing
that requires rake aside from running the spec suite) may work or be made to
work with older versions of rake. We would be happy to bump the dependency
down to 0.8.3 to provide out-of-the-box support for RHEL5 and will
gratefully accept patches that let us do that.

[1] See https://help.ubuntu.com/community/RubyOnRails
[2] http://docs.rubygems.org/read/chapter/3

On Tue, Dec 15, 2009 at 1:09 PM, jw2dot...@gmail.com wrote:

> Bummer.  Requires rake >= 0.8.4, but RHEL5/EPEL is only 0.8.3.
>
>
> http://download.fedora.redhat.com/pub/epel/5/x86_64/repoview/rubygem-rake.html
>
>
> On Dec 14, 3:29 pm, Rein Henrichs  wrote:
> > Greetings Puppeteers,
> >
> > It's the holidays once again and, in the spirit of the season, I bring
> you
> > the immediate release of Puppet Dashboard 0.1.0, codenamed "Wira".
> Because
> > the Wira is a car. From Malaysia. And cars have dashboards. Even cars
> from
> > Malaysia.
> >
> > This release includes run success and total run time graphs and a global
> > status drop-down tab that provides at-a-glance system status updates. We
> are
> > still deciding on which information to present where and how best to
> present
> > it, so expect these to change in upcoming releases as we converge on the
> > most useful set of data to display. Coincidentally, this would be a great
> > time to tell us which information is most important to you on which
> pages.
> > You could even reply to this message on the list if you want (hint).
> >
> > Also, at the request of just about everyone, I've posted a tour of the
> > latest Dashboard release on the Reductive Labs blog athttp://
> reductivelabs.com/2009/12/14/a-tour-of-puppet-dashboard-0-1-0. Yes,
> > it includes screenshots. Huzzah.
> >
> > Get the code athttp://github.com/reductivelabs/puppet-dashboard.
> > Submit feature requests and bug reports athttp://
> projects.reductivelabs.com/projects/dashboard.
> >
> > Have a great holiday season, folks.
> >
> > --
> > Rein Henrichshttp://reductivelabs.com
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
>


-- 
Rein Henrichs
http://reductivelabs.com

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Announcing Puppet Dashboard 0.1.0 Release

[jw2dot...@gmail.com]

Bummer.  Requires rake >= 0.8.4, but RHEL5/EPEL is only 0.8.3.

http://download.fedora.redhat.com/pub/epel/5/x86_64/repoview/rubygem-rake.html


On Dec 14, 3:29 pm, Rein Henrichs  wrote:
> Greetings Puppeteers,
>
> It's the holidays once again and, in the spirit of the season, I bring you
> the immediate release of Puppet Dashboard 0.1.0, codenamed "Wira". Because
> the Wira is a car. From Malaysia. And cars have dashboards. Even cars from
> Malaysia.
>
> This release includes run success and total run time graphs and a global
> status drop-down tab that provides at-a-glance system status updates. We are
> still deciding on which information to present where and how best to present
> it, so expect these to change in upcoming releases as we converge on the
> most useful set of data to display. Coincidentally, this would be a great
> time to tell us which information is most important to you on which pages.
> You could even reply to this message on the list if you want (hint).
>
> Also, at the request of just about everyone, I've posted a tour of the
> latest Dashboard release on the Reductive Labs blog 
> athttp://reductivelabs.com/2009/12/14/a-tour-of-puppet-dashboard-0-1-0. Yes,
> it includes screenshots. Huzzah.
>
> Get the code athttp://github.com/reductivelabs/puppet-dashboard.
> Submit feature requests and bug reports 
> athttp://projects.reductivelabs.com/projects/dashboard.
>
> Have a great holiday season, folks.
>
> --
> Rein Henrichshttp://reductivelabs.com

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Provider Augeas not functional on Sles10?

[David Lutterkort]

On Mon, 2009-12-14 at 08:24 -0800, Os wrote:
> Is there something else I am missing or does augeas and puppet do not
> work on Sles10 ?

As others have mentioned, you need the ruby-augeas bindings. Rather than
building them from a tarball/gem, you might try to find (a) an srpm from
OpenSuSe or (b) an srpm from Fedora/EPEL and rebuild one of those -
there shouldn't be very many surprises.

David


--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] puppet-dashboard

[Rein Henrichs]

Luke,

Upon further review of the play, apparently a migration file "went missing".
I'm not sure how, but it has been restored. Sorry about this bush league
slacker stuff, things should be working fine with the just released 0.1.1
code (or the code fresh off the HEAD of the master branch, which should be
stable at all times if you want the latest changes).

On Tue, Dec 15, 2009 at 11:36 AM, Rein Henrichs wrote:

> Luke,
>
> Interesting. I think the issue here is with migration order. The
> Report#success? method depends on the existence of a `success` boolean field
> on the reports table, which may happen at a later migration than when the
> method is called. Flattening the migrations into a single file should
> alleviate this and is also a good idea in general. I'll fix this ASAP and
> release a new point version.
>
> Thanks for the heads up.
>
> --
> Rein Henrichs
> http://reductivelabs.com
>



-- 
Rein Henrichs
http://reductivelabs.com

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] puppet-dashboard

[Rein Henrichs]

Luke,

Interesting. I think the issue here is with migration order. The
Report#success? method depends on the existence of a `success` boolean field
on the reports table, which may happen at a later migration than when the
method is called. Flattening the migrations into a single file should
alleviate this and is also a good idea in general. I'll fix this ASAP and
release a new point version.

Thanks for the heads up.

-- 
Rein Henrichs
http://reductivelabs.com

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] puppet-dashboard

[Baker, Luke Jefferson]

I'm trying to set up puppet-dashboard but I seem to have run into a roadblock: 
when executing 'rake install' the follow message gets returned..

rake aborted!
undefined method `success?' for #

If it makes a difference, I'm using an sqlite database. Any assistance would be 
much appreciated ;)

--Luke Baker

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] puppet-dashboard installation

[Luke Baker]

I’m trying to set up puppet-dashboard but I seem to have run into a
roadblock: when executing ‘rake install’ the follow message gets
returned..

rake aborted!
undefined method `success?' for #

If it makes a difference, I’m using an sqlite database. Any assistance
would be much appreciated ;)

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] AIX Puppet clients is not sending request for cert

[M.F.Haris]

yes, this is a problem but you can do add --server="your-server-address"
when executing the puppet at client's command prompt

Muhammad Haris Farooque
MSc. Software Engineering (Hochshule Für Technik-Stuttgart)
Home: +49-711-121-70007
Cell:+49-176-701-39163



On Mon, Dec 14, 2009 at 9:31 PM, Roberto Bouza  wrote:

> Hello,
>
> I was able to compile ruby add gems install facter and puppet on one
> LDAP. Now everything looks good, puppetd is up and running but when
> checking the certificate on the puppetmaster server (A linux box) I
> don't see the request from the client at all.
>
> Do you have any ideas?
>
> Thank you.
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
>

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] ACLs plugin

[Joe McDonagh]

jeanvaljean wrote:
> Hello everybody,
> I would like to know if there is a plugin that allow us to manage
> advances ACL on a linux system (Debian )
> Because for the moment,the idea to use "exec setfacl" to set my ACLs
> sounds a little bit "dirty"
> Thanks
>
> --
>
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>
>
>   
There is a feature request for this functionality.

The problem is that in the future, I am guessing filesystems will move 
towards the NFSv4 ACLs, but for now a POSIX draft ACL type would be nice...

For now, using exec is the only way to do it. You can wrap that up 
inside a define and call it facl, mimicking the functionality of an 
actual type.

-- 
Joe McDonagh
Silent Penguin Services
Operations Engineer
AIM: YoosingYoonickz
IRC: joe-mac on freenode
Blog: www.colonfail.com

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] ACLs plugin

[jeanvaljean]

Hello everybody,
I would like to know if there is a plugin that allow us to manage
advances ACL on a linux system (Debian )
Because for the moment,the idea to use "exec setfacl" to set my ACLs
sounds a little bit "dirty"
Thanks

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: problems with onlyif/unless directives

[sHaggY_caT]

I think, problems was resolved:

Exec with this "onlyif":

onlyif => "test `/root/test-new.sh ${veid} ${vetarif}` = 0 "

Run only if $veid=302:


Dec 15 19:12:19 vz-test puppetd[16426]: Starting catalog run
Dec 15 19:12:45 vz-test puppetd[16426]: (//Node[vz-test.local]/
Mod_class_ovzconfigs::Mod_def_ovzbackup[ovzserver_backup]/Cron
[incremental_backup]/weekday) defined 'weekday' as '*'
Dec 15 19:12:46 vz-test puppetd[16426]: (//Node[vz-test.local]/
Mod_class_ovzconfigs::Mod_def_veadm[customer2.vps.local]/Exec[vecfg-
applyset_customer2.vps.local]/returns) executed successfully
Dec 15 19:12:46 vz-test puppetd[16426]: Finished catalog run in 27.27
seconds


onlyif => "test `/root/test-new.sh ${veid} ${vetarif}` = 0 "


[r...@vz-test conf]# cat /root/test-new.sh
#!/bin/bash
if [[ $1 = 302 ]]
then echo 0
else echo 1
fi

Thank you for answer.

For another puppet users, who find this topic: try to use binary file
test for test with your custom scripts :))




On 15 дек, 11:12, sHaggY_caT  wrote:
> Hi John,
>
> Thank you for answer.
>
> > For debugging your manifests, you could try using
>
> >      unless => "/bin/true"
>
> > or
>
> >     unless => "/bin/false"
>
> > to take that test script out of the picture.
>
> Script, in "command" work fine.
>
> > Speaking of the test script, are you sure your nodes are getting and
> > using the correct version?
>
> It's use one version, without differents of number:
>
> [shaggy...@puppet ~]$ rpm -qa | grep puppet
> puppet-server-0.24.8-1.el5.1
> puppet-0.24.8-1.el5.1
> [shaggy...@puppet ~]$
>
> [r...@vz-test conf]# rpm -qa | grep puppet
> puppet-0.24.8-1.el5.1
> [r...@vz-test conf]#
>
> > As far as I know, Exec executes its command(s) directly, not via a
> > shell, so I would be surprised if that did what you expect,
> > independent of the "unless".  That is, "if" is a keyword in the sh
> > language, not an executable program (not on any system I'm familiar
> > with, anyway), so I would expect that Exec to fail every time it runs.
>
> OK, i think you true. Do you have means, how use bash script inside
> "onlyif"/"unless"?
> I try use script in command line:
>
> [r...@vz-test conf]# test "/usr/sbin/rc.test-parametrs-changed.sh
> check_settings 301 10.0.5.31 yes vps256M 10.0.5.52"
> [r...@vz-test conf]# echo $?
> 0
> [r...@vz-test conf]# /usr/sbin/rc.test-parametrs-changed.sh
> check_settings 301 10.0.5.31 yes vps256M 10.0.5.52
> [r...@vz-test conf]# echo $?
> 1
> [r...@vz-test conf]#
>
> but, bash exec(system command) return 0:
>
> [r...@vz-test conf]# bash /usr/sbin/rc.test-parametrs-changed.sh
> check_settings 301 10.0.5.31 yes vps756M 10.0.5.52
> [r...@vz-test conf]# echo $?
> 0
> [r...@vz-test conf]#
>
> but "unless" inside puppet exec run exec:
>
> exec { "vecfg-applyset_${name}":
>     command => "if [[ ( -d /vz/private/${veid} ) && ( -f /etc/
> sysconfig/vz-scripts/${veid}.conf) && \
>      ( $(/usr/sbin/rc.test-parametrs-changed.sh check_settings ${veid}
> ${veip} ${vetarif} ${vedns}  ; echo $?) -eq 1)]] ; \
>      then vzctl set ${veid}  --hostname ${vehostname} --ipadd ${veip}
> --nameserver ${vedns} --save; \
>      vzctl set ${veid} --applyconfig ${vetarif} --save;  fi",
>     path => ["/usr/bin", "/usr/sbin"],
>     unless => "bash /usr/sbin/rc.test-parametrs-changed.sh
> check_settings ${veid} ${veip} ${vetarif} ${vedns}",
>     }
>
> If/else inside "command" works, as i test (i use if/else inside
> command, becouse unless/onlyif does'nt work for me):
>
> [r...@vz-test conf]# cat ~/tmp_2 | grep -v  _off
> Dec 15 13:41:05 vz-test puppetd[23387]: Starting catalog run
> Dec 15 13:41:06 vz-test puppetd[23387]: (//Node[vz-test.local]/
> Mod_class_ovzconfigs::Mod_def_veadm[customer2.vps.local]/Exec[vecfg-
> applyset_customer2.vps.local]/returns) executed successfully
> Dec 15 13:41:16 vz-test puppetd[23387]: (//Node[vz-test.local]/
> Mod_class_ovzconfigs::Mod_def_ovzbackup[ovzserver_backup]/Cron
> [incremental_backup]/weekday) defined 'weekday' as '*'
> Dec 15 13:43:07 vz-test puppetd[23387]: (//Node[vz-test.local]/
> Mod_class_ovzconfigs::Mod_def_veadm[customer1.vps.local]/Exec[vecfg-
> applyset_customer1.vps.local]/returns) executed successfully
> Dec 15 13:43:14 vz-test puppetd[23387]: (//Node[vz-test.local]/
> Mod_class_ovzconfigs::Mod_def_veadm[customer4.vps.local]/Exec[vecfg-
> applyset_customer4.vps.local]/returns) executed successfully
> Dec 15 13:43:29 vz-test puppetd[23387]: Finished catalog run in 143.67
> seconds
>
>
>
> > You can have the puppetmaster distribute
> > it, but you may need to set up a require for it to make sure its
> > downloaded first.  (It's not clear from the docs whether Puppet will
> > autorequire it from the "unless" parameter.)  You'll also want to make
> > sure its ownership and permissions are set appropriately.
>
> > John

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email

Re: [Puppet Users] "no certificate found and waitforcert is disabled" on all new puppet clients

[paul matthews]

Silviu,

That fixed it. I had assumed removing the .pem file (
/etc/puppet/ssl/certs/client.hostname.pem
) would be enough but removing the whole directory was the answer

Thanks very much
Paul

2009/12/15 Silviu Paragina 

> This looks a lot like this problem:
> http://projects.reductivelabs.com/issues/2890
> Have you tried rm -rf /etc/puppet/ssl on the client? Or you are avoiding
> exactly that?
> In 0.25.1 puppet seems to force the usage of the cached certificates
> despite the fact that some of the data may be wrong, so you should try
> to clean the ca certificate (in case the ca certificate changed), the
> certificate request and as a last resort the private key. All this is
> done by the above rm. (not sure if you knew all that so that's why I'm
> mentioning).
>
>
>
> Silviu
>
> paul matthews wrote:
> > After further investigation it seems the problem exists with new
> > 0.25.1 clients
> >
> > On the server I run:-
> > puppetca --clean client.hostname
> >
> > On the client I run :-
> > rm /etc/puppet/ssl/certs/client.hostname.pem
> >
> > Followed by the command that brings up the error
> >
> > #  /opt/csw/bin/puppetd --trace --debug --test --factsync --server
> > server.hostname.com 
> >
> > debug: Failed to load library 'shadow' for feature 'libshadow'
> > debug: Puppet::Type::User::ProviderDirectoryservice: file
> > /usr/bin/dscl does not exist
> > debug: Puppet::Type::User::ProviderPw: file pw does not exist
> > debug: Failed to load library 'ldap' for feature 'ldap'
> > debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
> > debug: /File[/var/puppet/run/puppetd.pid]: Autorequiring
> > File[/var/puppet/run]
> > debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
> > File[/etc/puppet/ssl]
> > debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
> > File[/etc/puppet/ssl]
> > debug: /File[/var/puppet/lib]: Autorequiring File[/var/puppet]
> > debug: /File[/etc/puppet/ssl/private]: Autorequiring
> File[/etc/puppet/ssl]
> > debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
> > File[/etc/puppet/ssl]
> > debug: /File[/var/puppet/clientbucket]: Autorequiring File[/var/puppet]
> > debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
> > debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
> > File[/etc/puppet/ssl/certs]
> > debug: /File[/var/puppet/run]: Autorequiring File[/var/puppet]
> > debug: /File[/var/puppet/log]: Autorequiring File[/var/puppet]
> > debug: /File[/etc/puppet/ssl/private_keys/client.hostname.com.pem]:
> > Autorequiring File[/etc/puppet/ssl/private_keys]
> > debug: /File[/var/puppet/state/graphs]: Autorequiring
> > File[/var/puppet/state]
> > debug: /File[/var/puppet/state]: Autorequiring File[/var/puppet]
> > debug: /File[/var/puppet/facts]: Autorequiring File[/var/puppet]
> > debug: /File[/var/puppet/client_yaml]: Autorequiring File[/var/puppet]
> > debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
> > debug: /File[/etc/puppet/ssl/public_keys/client.hostname.com.pem]:
> > Autorequiring File[/etc/puppet/ssl/public_keys]
> > debug: Finishing transaction 75308830 with 0 changes
> > debug: Using cached certificate for ca
> > warning: peer certificate won't be verified in this SSL session
> > debug: Using cached certificate_request for client.hostname.com
> > 
> > debug: Using cached certificate for ca
> > warning: peer certificate won't be verified in this SSL session
> > debug: Using cached certificate for ca
> > warning: peer certificate won't be verified in this SSL session
> > Exiting; no certificate found and waitforcert is disabled
> >
> > I'm afraid it has me really stumped for ideas though
> >
> > Paul
> >
> > 2009/12/14 paul matthews  > >
> >
> > Thanks Ohad for pointing this out - schoolboy error on my part.
> > Unfortunately, this has not fixed things - both server and client
> > are running 25.1.
> > Do you know of anything else that may be causing this
> >
> > Thanks
> > Paul
> >
> > 2009/12/14 Ohad Levy mailto:ohadl...@gmail.com
> >>
> >
> > server must be newer or equal to the clients..
> >
> > Ohad
> >
> > On Mon, Dec 14, 2009 at 7:36 PM, paul matthews
> >  > > wrote:
> >
> > Hi,
> > I'm not too sure why this has cropped up after working
> > fine for months but on new clients  I get the following
> > errors:-
> > Thanks
> > # puppetd --test
> > warning: peer certificate won't be verified in this SSL
> > session
> > warning: peer certificate won't be verified in this SSL
> > session
> > warning: peer certificate won't be verified in this SSL
> > session
> > Exiting; no certificate found and waitforcert is disabled
> >
> > Most of the ar

[Puppet Users] generating rrds from reports

[Chad Huneycutt]

I have a bunch of puppet report files, and I would like to regenerate
the rrd files for those reports.  Can anyone tell me what the process
is to do that?

-- 
Chad M. Huneycutt

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] "no certificate found and waitforcert is disabled" on all new puppet clients

[Silviu Paragina]

This looks a lot like this problem: 
http://projects.reductivelabs.com/issues/2890
Have you tried rm -rf /etc/puppet/ssl on the client? Or you are avoiding 
exactly that?
In 0.25.1 puppet seems to force the usage of the cached certificates 
despite the fact that some of the data may be wrong, so you should try 
to clean the ca certificate (in case the ca certificate changed), the 
certificate request and as a last resort the private key. All this is 
done by the above rm. (not sure if you knew all that so that's why I'm 
mentioning).



Silviu

paul matthews wrote:
> After further investigation it seems the problem exists with new 
> 0.25.1 clients
>
> On the server I run:-
> puppetca --clean client.hostname
>
> On the client I run :-
> rm /etc/puppet/ssl/certs/client.hostname.pem
>
> Followed by the command that brings up the error
>
> #  /opt/csw/bin/puppetd --trace --debug --test --factsync --server 
> server.hostname.com 
>
> debug: Failed to load library 'shadow' for feature 'libshadow'
> debug: Puppet::Type::User::ProviderDirectoryservice: file 
> /usr/bin/dscl does not exist
> debug: Puppet::Type::User::ProviderPw: file pw does not exist
> debug: Failed to load library 'ldap' for feature 'ldap'
> debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
> debug: /File[/var/puppet/run/puppetd.pid]: Autorequiring 
> File[/var/puppet/run]
> debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring 
> File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring 
> File[/etc/puppet/ssl]
> debug: /File[/var/puppet/lib]: Autorequiring File[/var/puppet]
> debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring 
> File[/etc/puppet/ssl]
> debug: /File[/var/puppet/clientbucket]: Autorequiring File[/var/puppet]
> debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
> debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring 
> File[/etc/puppet/ssl/certs]
> debug: /File[/var/puppet/run]: Autorequiring File[/var/puppet]
> debug: /File[/var/puppet/log]: Autorequiring File[/var/puppet]
> debug: /File[/etc/puppet/ssl/private_keys/client.hostname.com.pem]: 
> Autorequiring File[/etc/puppet/ssl/private_keys]
> debug: /File[/var/puppet/state/graphs]: Autorequiring 
> File[/var/puppet/state]
> debug: /File[/var/puppet/state]: Autorequiring File[/var/puppet]
> debug: /File[/var/puppet/facts]: Autorequiring File[/var/puppet]
> debug: /File[/var/puppet/client_yaml]: Autorequiring File[/var/puppet]
> debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl/public_keys/client.hostname.com.pem]: 
> Autorequiring File[/etc/puppet/ssl/public_keys]
> debug: Finishing transaction 75308830 with 0 changes
> debug: Using cached certificate for ca
> warning: peer certificate won't be verified in this SSL session
> debug: Using cached certificate_request for client.hostname.com 
> 
> debug: Using cached certificate for ca
> warning: peer certificate won't be verified in this SSL session
> debug: Using cached certificate for ca
> warning: peer certificate won't be verified in this SSL session
> Exiting; no certificate found and waitforcert is disabled
>
> I'm afraid it has me really stumped for ideas though
>
> Paul
>
> 2009/12/14 paul matthews  >
>
> Thanks Ohad for pointing this out - schoolboy error on my part.
> Unfortunately, this has not fixed things - both server and client
> are running 25.1.
> Do you know of anything else that may be causing this
>
> Thanks
> Paul
>
> 2009/12/14 Ohad Levy mailto:ohadl...@gmail.com>>
>
> server must be newer or equal to the clients..
>
> Ohad
>
> On Mon, Dec 14, 2009 at 7:36 PM, paul matthews
>  > wrote:
>
> Hi,
> I'm not too sure why this has cropped up after working
> fine for months but on new clients  I get the following
> errors:-
> Thanks
> # puppetd --test
> warning: peer certificate won't be verified in this SSL
> session
> warning: peer certificate won't be verified in this SSL
> session
> warning: peer certificate won't be verified in this SSL
> session
> Exiting; no certificate found and waitforcert is disabled
>
> Most of the articles I've read suggest a much earlier bug.
>  As it's a closed test environment I've set autosign =
> true in /etc/puppet.conf
>
> Does anyone know how I get round this. Clients are running
> 0.25.1, server = 0.24.8
>
> Thanks
> Paul
>
>
> -- 
> Paul Matthews
> 
> -

[Puppet Users] Re: How to override / redefine outside child class (usecase and example detailled)

[jcbollinger]

On Dec 15, 4:03 am, Alexandre  wrote:
>    I though i found a way to do it, and i would like to show it here,
> but unfortunately it does not exactly work well, see the comment in
> uppercase: global variables seems to be set even if no class from
> the .pp file is included.

Yes.  Modules and manifest files do not provide scoping.

>    And i also think now i am going to far into akwardness, just trying

I agree (a bit more on that below).

> to work around some Puppet limitations, or maybe thinking of Puppet
> beyond its scope, as if it was a full featured language

Puppet is a declarative language.  Users who come from a programming
background seem sometimes to have difficulty coming to grips with
that.  If you ever find yourself thinking "how do a make Puppet do
foo?" then you are off to a wobbly start.  A better question is
usually "how do I explain foo to Puppet?".

>    I am wondering now if it is always a good idea to try to do
> everything within Puppet.

Puppet does have limits to what it can do natively for you (though it
is also highly extensible).  Where it is possible, using Puppet types
other than Exec to get the work done has several advantages.

[...]

> and ended up having this
> define only get the parameters and give it all to a deployed script
> that does the processing (just because i needed to loop on the items
> of a puppet array).

Puppet is not built to do user-defined processing, except inasmuch as
you can always create your own types and / or providers.

>    Anyway, here was my last, and almost working to get the default
> stripdown (shows relevant parts) :

[...]

> # This variable is global, not defined inside the class, otherwise it
> will never be seen as set, due to the dynamic scope
> $_service_is_managed_mysqld=1

So the idea is that you have a variable for each service that later
instructs Puppet whether to run "stripdown" commands for that
service?  And that implies that somewhere you dynamically choose a
value for this variable based on the facts presented to the
puppetmaster?

That seems awfully convoluted.  Why not use that same decision logic
to dynamically choose whether to include a class?  Furthermore, if you
have to make that decision dynamically, then it is no harder to choose
between two alternative classes than to make only a yes/no decision
about a single class.  That leads to having two alternative classes,
one declaring "stripdown"-configured resources and the other declaring
enabled resources, where you dynamically decide which to include for
each node.  And that's what I have been recommending all along.

[...]

>     if $pattern == "" {
>         exec { "stripdown $name stop":
>                 command => "service $name stop",
>                 onlyif  => "service $name status",
>                 path    => "/usr/bin:/usr/sbin:/bin:/sbin",
>             }
>     }

[etc.]

I'm not seeing what that "stripdown" define does for you that the
Service type doesn't, unless   Please tell me that you're not
using these Execs to change the state of Services declared elsewhere!
That way lies madness.

I guess I'm at a loss as to what problem you're trying to solve any
more.  Silviu and I offered two solutions to you, either one of which
will work cleanly and entirely within Puppet to solve your problem as
I understood it.  What more are you looking for that neither of these
provides?

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] "no certificate found and waitforcert is disabled" on all new puppet clients

[paul matthews]

After further investigation it seems the problem exists with new 0.25.1
clients

On the server I run:-
puppetca --clean client.hostname

On the client I run :-
rm /etc/puppet/ssl/certs/client.hostname.pem

Followed by the command that brings up the error

#  /opt/csw/bin/puppetd --trace --debug --test --factsync --server
server.hostname.com

debug: Failed to load library 'shadow' for feature 'libshadow'
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does
not exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Failed to load library 'ldap' for feature 'ldap'
debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
debug: /File[/var/puppet/run/puppetd.pid]: Autorequiring
File[/var/puppet/run]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/var/puppet/lib]: Autorequiring File[/var/puppet]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/var/puppet/clientbucket]: Autorequiring File[/var/puppet]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/puppet/run]: Autorequiring File[/var/puppet]
debug: /File[/var/puppet/log]: Autorequiring File[/var/puppet]
debug: /File[/etc/puppet/ssl/private_keys/client.hostname.com.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /File[/var/puppet/state/graphs]: Autorequiring
File[/var/puppet/state]
debug: /File[/var/puppet/state]: Autorequiring File[/var/puppet]
debug: /File[/var/puppet/facts]: Autorequiring File[/var/puppet]
debug: /File[/var/puppet/client_yaml]: Autorequiring File[/var/puppet]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/public_keys/client.hostname.com.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug: Finishing transaction 75308830 with 0 changes
debug: Using cached certificate for ca
warning: peer certificate won't be verified in this SSL session
debug: Using cached certificate_request for client.hostname.com
debug: Using cached certificate for ca
warning: peer certificate won't be verified in this SSL session
debug: Using cached certificate for ca
warning: peer certificate won't be verified in this SSL session
Exiting; no certificate found and waitforcert is disabled

I'm afraid it has me really stumped for ideas though

Paul

2009/12/14 paul matthews 

> Thanks Ohad for pointing this out - schoolboy error on my part.
> Unfortunately, this has not fixed things - both server and client are
> running 25.1.
> Do you know of anything else that may be causing this
>
> Thanks
> Paul
>
> 2009/12/14 Ohad Levy 
>
>> server must be newer or equal to the clients..
>>
>> Ohad
>>
>> On Mon, Dec 14, 2009 at 7:36 PM, paul matthews <
>> paulsmatth...@googlemail.com> wrote:
>>
>>> Hi,
>>> I'm not too sure why this has cropped up after working fine for months
>>> but on new clients  I get the following errors:-
>>> Thanks
>>> # puppetd --test
>>> warning: peer certificate won't be verified in this SSL session
>>> warning: peer certificate won't be verified in this SSL session
>>> warning: peer certificate won't be verified in this SSL session
>>> Exiting; no certificate found and waitforcert is disabled
>>>
>>> Most of the articles I've read suggest a much earlier bug.  As it's a
>>> closed test environment I've set autosign = true in /etc/puppet.conf
>>>
>>> Does anyone know how I get round this. Clients are running 0.25.1, server
>>> = 0.24.8
>>>
>>> Thanks
>>> Paul
>>>
>>>
>>> --
>>> Paul Matthews
>>> --
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Puppet Users" group.
>>> To post to this group, send email to puppet-us...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> puppet-users+unsubscr...@googlegroups.com
>>> .
>>> For more options, visit this group at
>>> http://groups.google.com/group/puppet-users?hl=en.
>>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-us...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscr...@googlegroups.com
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>
>
>
> --
> Paul Matthews
> --
>



-- 
Paul Matthews
--

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegr

[Puppet Users] Re: problems with onlyif/unless directives

[sHaggY_caT]

Hi John,

Thank you for answer.

> For debugging your manifests, you could try using
>
>  unless => "/bin/true"
>
> or
>
> unless => "/bin/false"
>
> to take that test script out of the picture.


Script, in "command" work fine.


> Speaking of the test script, are you sure your nodes are getting and
> using the correct version?

It's use one version, without differents of number:

[shaggy...@puppet ~]$ rpm -qa | grep puppet
puppet-server-0.24.8-1.el5.1
puppet-0.24.8-1.el5.1
[shaggy...@puppet ~]$

[r...@vz-test conf]# rpm -qa | grep puppet
puppet-0.24.8-1.el5.1
[r...@vz-test conf]#

> As far as I know, Exec executes its command(s) directly, not via a
> shell, so I would be surprised if that did what you expect,
> independent of the "unless".  That is, "if" is a keyword in the sh
> language, not an executable program (not on any system I'm familiar
> with, anyway), so I would expect that Exec to fail every time it runs.


OK, i think you true. Do you have means, how use bash script inside
"onlyif"/"unless"?
I try use script in command line:

[r...@vz-test conf]# test "/usr/sbin/rc.test-parametrs-changed.sh
check_settings 301 10.0.5.31 yes vps256M 10.0.5.52"
[r...@vz-test conf]# echo $?
0
[r...@vz-test conf]# /usr/sbin/rc.test-parametrs-changed.sh
check_settings 301 10.0.5.31 yes vps256M 10.0.5.52
[r...@vz-test conf]# echo $?
1
[r...@vz-test conf]#

but, bash exec(system command) return 0:

[r...@vz-test conf]# bash /usr/sbin/rc.test-parametrs-changed.sh
check_settings 301 10.0.5.31 yes vps756M 10.0.5.52
[r...@vz-test conf]# echo $?
0
[r...@vz-test conf]#

but "unless" inside puppet exec run exec:

exec { "vecfg-applyset_${name}":
command => "if [[ ( -d /vz/private/${veid} ) && ( -f /etc/
sysconfig/vz-scripts/${veid}.conf) && \
 ( $(/usr/sbin/rc.test-parametrs-changed.sh check_settings ${veid}
${veip} ${vetarif} ${vedns}  ; echo $?) -eq 1)]] ; \
 then vzctl set ${veid}  --hostname ${vehostname} --ipadd ${veip}
--nameserver ${vedns} --save; \
 vzctl set ${veid} --applyconfig ${vetarif} --save;  fi",
path => ["/usr/bin", "/usr/sbin"],
unless => "bash /usr/sbin/rc.test-parametrs-changed.sh
check_settings ${veid} ${veip} ${vetarif} ${vedns}",
}

If/else inside "command" works, as i test (i use if/else inside
command, becouse unless/onlyif does'nt work for me):

[r...@vz-test conf]# cat ~/tmp_2 | grep -v  _off
Dec 15 13:41:05 vz-test puppetd[23387]: Starting catalog run
Dec 15 13:41:06 vz-test puppetd[23387]: (//Node[vz-test.local]/
Mod_class_ovzconfigs::Mod_def_veadm[customer2.vps.local]/Exec[vecfg-
applyset_customer2.vps.local]/returns) executed successfully
Dec 15 13:41:16 vz-test puppetd[23387]: (//Node[vz-test.local]/
Mod_class_ovzconfigs::Mod_def_ovzbackup[ovzserver_backup]/Cron
[incremental_backup]/weekday) defined 'weekday' as '*'
Dec 15 13:43:07 vz-test puppetd[23387]: (//Node[vz-test.local]/
Mod_class_ovzconfigs::Mod_def_veadm[customer1.vps.local]/Exec[vecfg-
applyset_customer1.vps.local]/returns) executed successfully
Dec 15 13:43:14 vz-test puppetd[23387]: (//Node[vz-test.local]/
Mod_class_ovzconfigs::Mod_def_veadm[customer4.vps.local]/Exec[vecfg-
applyset_customer4.vps.local]/returns) executed successfully
Dec 15 13:43:29 vz-test puppetd[23387]: Finished catalog run in 143.67
seconds




> You can have the puppetmaster distribute
> it, but you may need to set up a require for it to make sure its
> downloaded first.  (It's not clear from the docs whether Puppet will
> autorequire it from the "unless" parameter.)  You'll also want to make
> sure its ownership and permissions are set appropriately.
>
> John

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Provider Augeas not functional on Sles10?

[Silviu Paragina]

Os wrote:
> No, I have just installed the 4 packages. How do I compile these
> bindings, I have not worked with ruby that much.
> I have downloaded "ruby-augeas-0.3.0.tgz" from "http://augeas.net/
> download/ruby/" but do not know how to go further.
> I need rake to compile this Rakefile?
>
>   
You may try (as it's easier) with the gem.
gem install ruby-augeas-0.x.x.gem


You will also need libaugeas-dev

Silviu


--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: How to override / redefine outside child class (usecase and example detailled)

[Alexandre]

   I though i found a way to do it, and i would like to show it here,
but unfortunately it does not exactly work well, see the comment in
uppercase: global variables seems to be set even if no class from
the .pp file is included.
   And i also think now i am going to far into akwardness, just trying
to work around some Puppet limitations, or maybe thinking of Puppet
beyond its scope, as if it was a full featured language
   I am wondering now if it is always a good idea to try to do
everything within Puppet. I think if i get time, i will do a generic
script to address this problem, which would be deployed with the usual
set of scripts i deploy on each server, and run it from Puppet. I also
recently went onto another set of Puppet problem, to which i began
implementing a define to do some processing, and ended up having this
define only get the parameters and give it all to a deployed script
that does the processing (just because i needed to loop on the items
of a puppet array).

   Anyway, here was my last, and almost working to get the default
stripdown (shows relevant parts) :

##
## mysqld.pp
##

# This variable is global, not defined inside the class, otherwise it
will never be seen as set, due to the dynamic scope
$_service_is_managed_mysqld=1
class mysql::server inherits mysql {
# (...)
}


##
## stripdown.pp
##

define stripdown_service ( $pattern="" ) {

if $pattern == "" {
exec { "stripdown $name stop":
command => "service $name stop",
onlyif  => "service $name status",
path=> "/usr/bin:/usr/sbin:/bin:/sbin",
}
} else {
exec { "stripdown $name stop":
command => "service $name stop",
onlyif  => "pgrep -f \"$name\"",
path=> "/usr/bin:/usr/sbin:/bin:/sbin",
}
}

exec { "stripdown $name deactivate":
command => "chkconfig $name off",
onlyif  => "chkconfig $name",
path=> "/usr/bin:/usr/sbin:/bin:/sbin",
}
}

class stripdown_services::centos {
service {
"autofs": enable => "false", ensure => "stopped";
"avahi-daemon": enable => "false", ensure => "stopped";
# (...)
}

# THIS $_service_is_managed_xxx THING DOES NOT WORK : EVEN IF NOT
CLASS NOT INCLUDED IN THE NODE, THE VARIABLE SEEMS TO BE SET !!!

if $_service_is_managed_squid != 1 { stripdown_service{squid:} }
if $_service_is_managed_lighttpd != 1 { stripdown_service
{lighttpd: pattern=>"lighttpd.conf"} }
if $_service_is_managed_mysqld != 1 { stripdown_service{mysqld:} }
# (...)
}


--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Installing Specific RPM Version

[Silviu Paragina]

Douglas Garstang wrote:
> Silviu,
>
> My system is aware of both the -1 and -2 releases in the repo.
>
> This is before running puppet...
>
> papp1 ~:# yum list tf-elements-core-tfel0-14.3-1.tf
> [ stuff removed ]
> Available Packages
> tf-elements-core-tfel0.noarch
> 14.3-1.tf
>
> papp1 ~:# yum list tf-elements-core-tfel0-14.3-2.tf
> [ stuff removed ]
> Available Packages
> tf-elements-core-tfel0.noarch
> 14.3-2.tf
>
> My manifest has:
>
> package {
> "tf-elements-core-14.3-1.tf":
> ensure => "${release}";
> }
>
> and here's what puppet logs when it barfs:
>
> debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q
> tf-elements-core-tfel0 --nosignature --nodigest --qf %{NAME}
> %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}
> '
> debug: 
> //Node[papp1.fr.twofish.com]/Elements::Setup[tfel0]/Package[tf-elements-core-tfel0]:
> Changing ensure
> debug: 
> //Node[papp1.fr.twofish.com]/Elements::Setup[tfel0]/Package[tf-elements-core-tfel0]:
> 1 change(s)
> debug: Package[tf-elements-core-tfel0](provider=yum): Ensuring => 14.3-1.tf
>   

> debug: Puppet::Type::Package::ProviderYum: Executing '/usr/bin/yum -d
> 0 -e 0 -y install tf-elements-core-tfel0-14.3-1.tf'
> debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q
> tf-elements-core-tfel0 --nosignature --nodigest --qf %{NAME}
> %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}
>   
Here puppet tells you what it is doing. This output leads me to believe 
that "/usr/bin/yum -d 0 -e 0 -y install 
tf-elements-core-tfel0-14.3-1.tf" ends with an error, but I might be 
wrong considering the fact that I haven't ever used yum, and I have 
failed to use rpm (back when I was a newbie using redhat).

Try switching the versions again and run these two commands puppet used, 
adding a "&& echo Return code OK" for each just to be sure that the 
return value is ok and see what you get.

SIDENOTE: this is a way of debugging something that isn't working in 
puppet :-) execs or anything else.

Silviu

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Provider Augeas not functional on Sles10?

[Os]

No, I have just installed the 4 packages. How do I compile these
bindings, I have not worked with ruby that much.
I have downloaded "ruby-augeas-0.3.0.tgz" from "http://augeas.net/
download/ruby/" but do not know how to go further.
I need rake to compile this Rakefile?

On 14 Dez., 22:52, Dan Bode  wrote:
> Did you compile the ruby augeas bindings?
>
> On Mon, Dec 14, 2009 at 8:24 AM, Os  wrote:
> > Hi,
> > I have a problem with augeas, puppet and Suse 10 SP2.
> > Augeas works when I use the augtool to edit files. But I would like to
> > use it in combination with puppet. My class looks something like this:
> >    augeas {"sysctl.conf":
> >            provider => "augeas",
> >            context => "/files/etc/sysctl.conf",
> >            changes => [
> >                "set net.core.wmem_default 262144",
> >                "set net.core.wmem_max 262144",
> >                "set kernel.sem 250        32000   100      128",
> >            ],
> >    }
>
> > When I do a 'puppetd -v -d --no-daemonize --onetime' on my node, I get
> > the following error:
> > "err: //Node...Failed to retrieve current state of resource: Provider
> > augeas is not functional on this platform"
>
> > I have installed the following packages:
> > # yum list | grep augeas
> > augeas.x86_64                     0.5.0-3.1                installed
> > augeas-devel.x86_64               0.5.0-3.1                installed
> > augeas-lenses.x86_64              0.5.0-3.1                installed
> > libaugeas0.x86_64                 0.5.0-3.1                installed
>
> > Is there something else I am missing or does augeas and puppet do not
> > work on Sles10 ?
>
> > Greetings,
> > Os
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Puppet Users" group.
> > To post to this group, send email to puppet-us...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscr...@googlegroups.com
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/puppet-users?hl=en.

--

You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.