Hello All
Well, I quickly packaged up puppet-2.6.5-rc1 and dropped it on my test VM
(Solaris 10 U9) against my 2.6.4 server, and immediately started getting the
same error message, but on different manifests, or the same manifests but
different line numbers. These manifests were written in 0.25.5
On Feb 4, 12:00 am, Jacob Helwig ja...@puppetlabs.com wrote:
- Forwarded message from Nick Lewis n...@puppetlabs.com -
essage-ID:
aanlktikjfwz98p_ncxf54zhbu2mjf15xdrlg2cmp2...@mail.gmail.com
We're back with a maintenance release: 2.6.5. This
release addresses a number of bugs in the
I'm working on a system for auto-resigning certificates for our clients and
Iv'e basically got it working .. but I notice that Puppet uses an inventory
file and a serial # file that seem to be differently formatted than the openssl
toolkit uses? The serial number file that puppet generates has
Because I like to live dangerously I upgraded to 2.6.5 and it seems like
this has resolved the CPU problem completely for me.
On Tue, Feb 1, 2011 at 3:17 PM, Udo Waechter udo.waech...@uni-osnabrueck.de
wrote:
On 01.02.2011, at 18:14, Brice Figureau wrote:
On Tue, 2011-02-01 at 10:30 -0500,
Hi,
this puppet.conf (excerpted):
[main]
logdir=/var/log/puppet { owner = ffrank, mode = 755 }
is supposed to change the owner of the logdir but won't:
# puppet master --no-daemonize --color false --masterport 8145
--pidfile=/var/run/puppet/master.debug.pid
While working on a bunch of freebsd servers, one feature that I found
lacking was the ability to nicely modify rc.conf variables (eg:
item_flags=--something) for installed ports/applications and have a
service do dependency checking so it restarts if it changes.
So a wrote a new puppet type
On 07/02/11 17:23, Ashley Penney wrote:
Because I like to live dangerously I upgraded to 2.6.5 and it seems like
this has resolved the CPU problem completely for me.
Did you upgrade the master or the master and all the nodes?
I had a discussion about this issue with Nigel during the week-end,
Did you ever files these bugs in the tracker?
On Feb 1, 2011, at 7:35 PM, Barry Jaspan wrote:
I'm using puppet 0.25.5 and just discovered two file resource bugs. I suspect
the bugs did not exist in 0.24 because the code were using that triggers them
has been the same for a long time and
I just upgraded the master, I was too lazy to do the nodes yet.
On Mon, Feb 7, 2011 at 1:56 PM, Brice Figureau
brice-pup...@daysofwonder.com wrote:
On 07/02/11 17:23, Ashley Penney wrote:
Because I like to live dangerously I upgraded to 2.6.5 and it seems like
this has resolved the CPU
I'm having a bit of trouble figuring out the best way to do my puppetdoc
stuff. I hope to have actual tutorial introductory chapter type
documentation as well as individual module documentation, but it seems
like all the examples I can find merely re-state the parameters that
puppetdoc already
Hi,
First, I'm sorry to hear you have any issues with puppetdoc (and before
you ask yourself why I started like this, I wrote the tool :).
On 07/02/11 20:19, Nick Moffitt wrote:
I'm having a bit of trouble figuring out the best way to do my puppetdoc
stuff. I hope to have actual tutorial
hello puppet list!
I am having some difficulty setting the correct baseurl setting for a
yum repo I am attempting to include in my puppet config.
Here is the error I am getting when I run puppetd --test
[root@VIRTCENT02:/etc/yum.repos.d] #puppetd --test
info: Caching catalog for
Did you escape the $basearch with a back-slash in your manifest?
baseurl = http://download.fedoraproject.org/pub/epel/5/\$basearch;,
-Mark
On Feb 7, 2011, at 2:57 PM, Tim Dunphy wrote:
hello puppet list!
I am having some difficulty setting the correct baseurl setting for a
yum repo I am
I've got a 4-server puppetmaster farm setup.. one server (master100) is the ca
master, all the others are just compile-time hosts. I was experimenting with
the facts_terminus = rest options and the inventory service, and found that as
soon as I turned on facts_terminus = rest on say master101,
We have a command line utility that queries a database to get certain
facts about our hosts -- I wanted to write a custom function to obtain
all of those facts at once. The tool outputs JSON and I wanted to
take that output and return a hash back into puppet where I could
access the facts like...
Ok, I was mistaken. Returning a hash works. It would be helpful if
the ruby exceptions bubbled up to puppet reported the correct line
number from the ruby source -- if that is possible.
Rich
On Mon, Feb 7, 2011 at 4:18 PM, Rich Rauenzahn rraue...@gmail.com wrote:
We have a command line
Hi,
I've run into some bug today with nagios checks that are exported in a
client's puppet setup.
The problem is that some host definitions are exported with an internal
address (10.x or 192.168.x) even though the servers do have an external
IP on another interface.
One of those uses a tap
hello puppet!!
I am attempting to install multiple yum repos in one of my manifests,
but am expressing this incorrectly (and hopefully only slightly)...
how may I express this idea appropriately in puppet?
class centos {
yumrepo { epel-repo:
baseurl =
On Feb 7, 2011, at 6:14 PM, Gabriel Filion wrote:
Hi,
I've run into some bug today with nagios checks that are exported in a
client's puppet setup.
The problem is that some host definitions are exported with an internal
address (10.x or 192.168.x) even though the servers do have an
On Mon, Feb 07, 2011 at 12:30:29PM -0500, Ross W wrote:
While working on a bunch of freebsd servers, one feature that I found
lacking was the ability to nicely modify rc.conf variables (eg:
item_flags=--something) for installed ports/applications and have a
service do dependency checking so it
20 matches
Mail list logo
