Re: [Puppet Users] Re: CentOS 5 packages in EPEL are outdated ?
Julien C. wrote: Answering to myself: no 2.6.14 doesn't send reports. Is this only an issue with integrating with dashboard or are you not getting reports at all with 2.6.14? I'm using the EPEL packages and my reports are working AFAICT. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The most overlooked advantage to owning a computer is that if they foul up, there's no law against whacking them around a little. -- Eric Porterfield pgplF0yVHXz9J.pgp Description: PGP signature
Re: [Puppet Users] Re: CentOS 5 packages in EPEL are outdated ?
Julien C. wrote: The dashboard integration part. I ended up using yup.puppetlabs.com and it works fine :-) Good to know. I wonder if the dashboard packages should require puppet >= 2.7.x ? -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ You pretend to work, and we'll pretend to pay you. pgpEEm9wFmrhQ.pgp Description: PGP signature
Re: [Puppet Users] Supported Ruby Versions for Telly
Gary Larizza wrote: Have you checked out the packages that Karanbir Singh has created? They work fairly well --> http://centos.karan.org/el5/ruby187/ They're also not updated for recent security vulnerabilities, which should be a concern for anyone deploying them in production. Basically, this means that Telly won't support el5 as a master, right? -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The most overlooked advantage to owning a computer is that if they foul up, there's no law against whacking them around a little. -- Eric Porterfield pgpxRuPkSIdmG.pgp Description: PGP signature
Re: [Puppet Users] Telly: Nagios types moving into Module
Michael Stahnke wrote: For the next major Puppet version, code-named Telly, we have some changes coming. This is the first in a series of emails around these changes and may require some input from the community. For Telly, the nagios types will be moved into a module. This allows them to be iterated on in isolation from the rest of Puppet's core release cycle and process. In the future we have plans to move several other types into modules that can be individually maintained, improved, tested and used. The module for Nagios will be available on the Forge. The upgrade path is the thing we need some feedback about. The basic steps to upgrade would be to setup a Telly master, and then install the Nagios module via the Puppet Module Tool, which ships integrated with 2.7.13+ and Telly. Is it possible to package these modules for distros? In the past, we've had a few requests to do this for third-party modules but we didn't do this because there wasn't really any standard for it. With puppet module tool being integrated now, perhaps that's something that can be reconsidered. I'm thinking that for folks using rpm, they'd rather see an update that pulls in the same fucntionality as they had before. And even for new installs, I'd personally prefer to install these things via rpm. If I wanted to use a secondary package management system, I could use gems or eggs or CPAN, but I don't. ;) I think it's good to split out these things, as it would allow us to properly add a nagios dep to the hypothetical puppet-module-nagios package. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ I am free of all prejudice. I hate everyone equally. -- W. C. Fields pgpimlSvSIWQQ.pgp Description: PGP signature
Re: [Puppet Users] Service Puppetmaster being monitored by Nagios
Hi,
Wendell Araujo wrote:
I have a server running Nagios and would like to monitor the service
in my puppet server puppetmaster. Has anyone managed to do this?
The REST API¹ is very handy for doing this.
I use https://$server:8140/production/status/no_key for this.
I had to allow this in the auth.conf on 2.6 (which I think is a bug
that may be fixed in 2.7). Without an auth.conf, this should be
allowed by default. The auth.conf changes:
# allow all nodes to access the server status
path /status
method find
allow *
The server picks this change up automatically, no need to restart it.
This allows a check like this:
sudo curl -s -H 'Accept: pson' \
--cacert /var/lib/puppet/ssl/certs/ca.pem \
--cert /var/lib/puppet/ssl/certs/$fqdn.pem \
--key /var/lib/puppet/ssl/private_keys/$fqdn.pem\
https://$server:8140/production/status/test
I use pycurl to wrap this all up in a check that tests that the URL
returns the expected out ({"is_alive":true}) and that it does so in
reasonable time. I've attached that check. If anyone finds this
useful and has improvements, feel free to drop me a line or send me a
diff.
¹ http://docs.puppetlabs.com/guides/rest_api.html
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Profanity is the inevitable linguistic crutch of the inarticulate
motherfucker.
-- Bruce Sherrod
#!/usr/bin/python -tt
#
# Copyright 2012 Todd Zullinger
#
# Permission to use, copy, modify, distribute, and sell this software and its
# documentation for any purpose is hereby granted without fee, provided that
# the above copyright notice appear in all copies and that both that
# copyright notice and this permission notice appear in supporting
# documentation. No representations are made about the suitability of this
# software for any purpose. It is provided "as is" without express or
# implied warranty.
"""Check puppetmaster via the REST API.
http://docs.puppetlabs.com/guides/rest_api.html
"""
import os
import re
import sys
import socket
import optparse
import cStringIO
# Handle import failures for non-standard modules
try:
import pycurl
import simplejson
except ImportError, error:
print 'UNKNOWN: Python import failure: %s' % error
sys.exit(3)
fqdn = socket.getfqdn()
ssldir = '<%= Puppet[:ssldir] %>'
defaults = {
'cacert': os.path.join(ssldir, 'certs/ca.pem'),
'cert': os.path.join(ssldir, 'certs/%s.pem' % fqdn),
'key': os.path.join(ssldir, 'private_keys/%s.pem' % fqdn),
'url': 'https://<%= fqdn %>:<%= scope.lookupvar("puppet::masterport")
%>/production/status/test',
'warn': 1.0,
'crit': 5.0,
'timeout': 10.0,
}
# Helper functions for nagios
def unknown(msg):
print 'UNKNOWN: %s' % msg
sys.exit(3)
def crit(msg):
print 'CRIT: %s' % msg
sys.exit(2)
def warn(msg):
print 'WARN: %s' % msg
sys.exit(1)
def ok(msg):
print 'OK: %s' % msg
sys.exit(0)
class CertError(StandardError):
"""Exception raised on certificate errors."""
pass
def certtest(path):
"""Check whether a cert/key file exists and can be accessed."""
if not os.path.exists(path):
parts = os.path.dirname(path).split(os.sep)
while parts:
testpath = os.sep.join(parts) or '/'
dummy = parts.pop()
status = os.access(testpath, os.R_OK)
if not status:
raise CertError('%s cannot be read' % testpath)
raise CertError('%s does not exist' % path)
if not os.access(path, os.R_OK):
raise CertError('%s cannot be read' % path)
if not os.path.getsize(path):
raise CertError('%s is empty' % path)
return True
def main():
formatter = optparse.IndentedHelpFormatter(width=100)
parser = optparse.OptionParser(formatter=formatter)
parser.add_option('--cacert', metavar='PATH', default=defaults['cacert'],
help='CA Certificate [%default]')
parser.add_option('--cert', metavar='PATH', default=defaults['cert'],
help='Client Certificate [%default]')
parser.add_option('--key', metavar='PATH', default=defaults['key'],
help='Client Key [%default]')
parser.add_option('--url', metavar='URL', default=defaults['url'],
h
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.9rc1 is available
Michael Stahnke wrote: > This release is a maintenance release of the 2.6.x series of Puppet. > > This release is available for download at: > http://puppetlabs.com/downloads/puppet/puppet-2.6.9rc1.tar.gz Better late than never, I've pushed rpm's for this release to my fedorapeople.org repo: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues Please note that 2.6.6 is in Fedora and EPEL testing repositories. I don't plan to update puppet there until 2.6.6 is pushed to the stable updates repos. Any help testing the 2.6.6 packages is most welcome. Once that update is stable, we'll be better able to more closely track the 2.6.x updates in the official repos. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Anyone who hates children and animals can't be all bad. -- W.C. Fields pgpNFxCQHenAf.pgp Description: PGP signature
Re: buglet (with rpms from tmz) Re: [Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.9rc1 is available
Hi, Christopher McCrory wrote: > I don't know if this is a rpm buglet or a general puppet buglet, but > with puppet-2.6.9-0.1.rc1.el5.noarch.rpm from tmz I get emails like: > > Wed Jun 22 12:46:11 -0700 2011 Puppet (notice): Finished catalog run in > 6.53 seconds > > on every run. I haven't tested the final release as I am going to test > 2.7.0 with ruby 1.9.2 instead. Is this different than with 2.6.8? This is definitely not something caused by the packaging, so if it's changed for the worse in some way, you'd want to file it in the puppetlabs.com issue tracker. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The nice thing about egotists is that they don't talk about other people. -- Lucille S. Harper pgpKMhJTCn6RU.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] Announce: 2.6.9 Released
Michael Stahnke wrote: > This release is a maintenance release of the 2.6.x series of Puppet. > This will likely be the last release in the 2.6.x series for Puppet, > now that 2.7 is out. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The policy of the American government is to leave its citizens free, neither restraining nor aiding them in their pursuits. -- Thomas Jefferson pgpahUZCkNB3g.pgp Description: PGP signature
Re: [Puppet Users] Re: [Puppet-dev] Announce: 2.6.9 Released
Hi Derek, Derek J. Balling wrote: > Do you have an ETA for 2.7.x RPMs in that repo by any chance? I'd like to get 2.6.6 into EPEL and then update it to 2.6.9 before I move my fedorapeople repo to 2.7.x. I've not looked closely at 2.7.x yet, but I get the feeling that it's not going to be an update we can push into EPEL. But maybe I'm mistaken about that. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Nothing in education is so astonishing as the amount of ignorance it accumulates in the form of inert facts. --Henry Brooks Adams pgp8zQ2zhPRwx.pgp Description: PGP signature
Re: [Puppet Users] Puppet 2.7.x and Facter 1.6 packages for Redhat/CentOS 5
rvlinden wrote: > I used to download the Puppet and Facter RHEL5 rpm packages from > http://people.fedoraproject.org/~tmz/repo/puppet/epel/ > > but the latest version on that site is puppet 2.6.9 and facter > 1.5.9. > > Does anyone know if this site is the still maintained ? or if there > are other locations where the rpm's are published Yes, it's still maintained. I need to get puppet 2.6.x pushed into Feodra and EPEL stable repos before I want to push 2.7.x into the fedorapeople.org repos. I haven't had enough time the past few weeks to make that happen, so I'm a little behind. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Teach a man to make fire, and he will be warm for a day. Set a man on fire, and he will be warm for the rest of his life. -- John A. Hrastar pgpEfCWDclarK.pgp Description: PGP signature
Re: [Puppet Users] Puppet RPM's
Douglas Garstang wrote: > Does anyone know where I can get the latest puppet, 2.7.1 as RPM's? > > The spec file that comes with the puppet 2.7.1 source is broken > again, and only version 0.25.5 seems to be available via EPEL, which > means that the website's assertion that you can get puppet as an RPM > from there is somewhat untrue. FWIW, 2.6.6 is in epel-testing (and has been for a while). We're not likely to jump on 2.7.x in EPEL for a while, as it brings several incompatible changes and still is early in it's life, so it has some issues that need shaken out. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Damn you vile woman, you've impeded my work since the day I escaped your vile womb! -- Stewie Griffin pgppuuMFzUzkE.pgp Description: PGP signature
Re: [Puppet Users] Re: Puppet RPM's
treydock wrote: > Here's a diff for version 2.6.9...all you have to do is change the > Version number. I added ruby-shadow cause I have had problems in 5.6 > with the "dist" variable not being set. If you're building packages and not using mock (which you should definitely check out, if you aren't), you want to pass in a few variables to ensure that the BuildRequire's and other features are taken care of properly. Something like this should do: rpm --define 'dist .el5' --define 'rhel 5' -ba puppet.spec Replace/modify dist and rhel as appropriate, though note that you still want to use rhel on CentOS and other EL rebuilds. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ It is impossible to enjoy idling thoroughly unless one has plenty of work to do. -- Jerome K. Jerome pgpWELGHNrFgS.pgp Description: PGP signature
Re: buglet (with rpms from tmz) Re: [Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.9rc1 is available
Chris May wrote: > Did anyone ever post a bug, or find a solution for this? I've just > upgraded some of our Solaris boxes (using OpenCSW) to 2.6.9 and I'm > seeing the same behaviour. If there is a bug filed, I'd love to know what it is. Searching redmine for "reports" doesn't find anything that looks like the right ticket. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ You can make it illegal, but you can't make it unpopular. -- Anonymous pgpA9jpOdv5xT.pgp Description: PGP signature
[Puppet Users] Sarasota meet up?
Hi all, I find myself in (generally) sunny Sarasota Florida for a few weeks. Any folks in the area want to meet up for drinks and puppet chatter? -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Subtlety is the art of saying what you think and getting out of the way before it is understood. -- Anonymous pgpeqyFQ48cbv.pgp Description: PGP signature
Re: buglet (with rpms from tmz) Re: [Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.9rc1 is available
I wrote: > Chris May wrote: >> Did anyone ever post a bug, or find a solution for this? I've just >> upgraded some of our Solaris boxes (using OpenCSW) to 2.6.9 and I'm >> seeing the same behaviour. > > If there is a bug filed, I'd love to know what it is. Searching > redmine for "reports" doesn't find anything that looks like the right > ticket. This looks to be https://projects.puppetlabs.com/issues/9167 and the patch there fixes the problem. I've updated the 2.6.9 packages on fedorapeople.org for Fedora and EPEL. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ A penny saved kills your career in government. pgpR1tRzPpa5X.pgp Description: PGP signature
Re: [Puppet Users] small problem with init script on RHEL6
Jim N wrote: > I was getting this when starting puppetmasterd (puppet- > server-0.25.5-1.el6.noarch RPM install): > > $ sudo /etc/init.d/puppetmaster start > Starting puppetmaster: Could not run: Could not create PID file: /var/ > lib/puppet/run/puppetmasterd.pid > > > This change in the init script fixed the problem: > > #pidfile=/var/run/puppet/puppetmasterd.pid > pidfile=/var/lib/puppet/run/puppetmasterd.pid > > Is that a bug worth reporting? I'm guessing you've changed puppet.conf such that it's not using /var/run/puppet/puppetmasterd.pid. Can you run: rpm -V puppet puppet-server ? If any files are modified, check how they differ from the shipped files. We won't be fixing any issues in puppet-0.25.5 in EPEL, as we've got 2.6.x in testing already. (In 2.6.x, the pid files have changed names, but the path is the same.) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ There is nothing government can give you that it hasn't taken from you in the first place. -- Winston Churchill pgpJim3fwl0iv.pgp Description: PGP signature
Re: [Puppet Users] Custom facts not working
Stefan Schulte wrote: > I guess facter as a standalone executable doesn't look into > /var/lib/puppet. Try running > > FACTERLIB=/var/lib/puppet/lib/facter facter > > as described in the custom facts guide [1] > > [1] http://docs.puppetlabs.com/guides/custom_facts.html#an-example Or use the -p | --puppet option to facter. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ When buying and selling are controlled by legislation, the first things to be bought and sold are legislators. -- P.J. O'Rourke pgpOMH6AWB3Wv.pgp Description: PGP signature
Re: [Puppet Users] Service issue/question
Sam Roza wrote:
> I think that the issue is due to my puppet installation (from EPEL)
> not configuring the init.d script properly.
It's configured fine as it is. :)
> puppetmasterd doesn't think it is a service.
You want to use service { 'puppetmaster': ... } in your manifests.
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
A penny saved kills your career in government.
pgpVWg7xOuruH.pgp
Description: PGP signature
Re: [Puppet Users] Re: Redhat and Scientific Linux
Johan Sunnerstig wrote: > That sounds promising. I'm currently using the EPEL repository to > install Puppet, and they're at 1.6.0. > I guess I'll have to decide what's less trouble, installing Puppet > some other way or rewriting a bunch of manifests. :) 1.6.1 is in epel-testing. Once it moves to stable, we'll push 1.6.2. (This process can be sped up if EPEL users snag a Fedora account and use the Bodhi update tool¹ to give positive or negative feedback on updates.) ¹ https://admin.fedoraproject.org/updates -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ To grasp the true meaning of socialism, imagine a world where everything is designed by the post office, even the sleaze. -- P.J. O'Rourke pgp8v7wrglx30.pgp Description: PGP signature
Re: [Puppet Users] Re: Redhat and Scientific Linux
Steve Traylen wrote: > The recently released facter contains a new fact $osfamily > > Facter 1.6.2. available > > ##New fact: (6792) Added osfamily fact. > >Added osfamily fact to determine if a given operating system is a >derivative of a common operating system. > > this is equal to redhat for redhat, centos, sl, slc, slf, sld, ... One thing that might make this fact less useful for folks that have both EL and Fedora systems is that Fedora is in the same osfamily. That makes sense in some cases and not in others. I've yet to start using this fact in my own manifests, so I'm not sure whether I'll like it or not. :) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ It's always darkest just before it goes pitch black. -- Demotivators (www.despair.com) pgpuWtBRTsBNc.pgp Description: PGP signature
Re: [Puppet Users] Puppet on Centos 6.0
robert.morti...@gmail.com wrote: > I am having no joy installing Puppet Server with MySQL support from > the EPEL on Centos 6. The active record support for MySQL seems to be > missing. Has anyone seen a good howto for this? Sadly, rubygem-rails is not built for EL-6. You can either rebuild the 2.3.8 packages from Fedora or find someone to act as a maintainer for these in EPEL. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ A word to the wise ain't necessary -- it's the stupid ones who need the advice. -- Bill Cosby pgpS6DaMfMzvl.pgp Description: PGP signature
Re: [Puppet Users] How to debug intermittent puppet catalog failure
Jo Rhett wrote: > Are you running the latest centos or redhat-based kernel? If so, > 274.7.1 is corked. Backgrade from 274.7.1 to 274.3.1 and the problem > will disappear. This is documented in > > https://projects.puppetlabs.com/issues/10418 > > And RedHat bug > > https://bugzilla.redhat.com/show_bug.cgi?id=751214 Thanks for filing that Jo. I've found the same issue on my CentOS systems. Can you mark that bug as public or ask the RHEL folks to do so? Right now, it's not accessible to most folks -- myself included. As one of the EPEL puppet maintainers, I'd very much like to be able to follow the discussion there. Perhaps if the bug can't be made public, I could get on the Cc? Thanks, -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ If God had meant for us to be naked, we would have been born that way. pgpFWNhwC3Cjt.pgp Description: PGP signature
Re: [Puppet-dev] Re: [Puppet Users] Puppet Dashboard packages now available!
James Cammarata wrote: > Any idea if/when these will be available in EPEL? Bundled rails and various gems will make that difficult, unfortunately. I don't know all that much about rails and gems, but if anyone knows if it's possible to cleanly install multiple versions of rails and gems, I'd be curious. If we were able to ship at least several major versions of rails in parallel, it might make it possible to package more recent tools like dashboard in Fedora and EPEL. But as long the rails stack encourages vendoring so extensively, no packages which do this will be acceptable for Fedora and EPEL. The rationale for not allowing bundled libraries (except in rare circumstances) is here: https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries Debian has a similar policy, I believe. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ I do not want people to be agreeable, as it saves me the trouble of liking them. -- Jane Austen pgpP9zFSJ5GF6.pgp Description: PGP signature
Re: [Puppet Users] Puppetmaster with stored configs leaks file descriptors on CentOS 5
Arnaud Gomes-do-Vale wrote: > Brice Figureau writes: > >> Can you try with a newer rails/active record? This one is a little >> bit old, and I'm not sure there aren't some bugs. I vaguely >> remember that puppet required rails 2.2, but I might be wrong. Well, puppet 0.25 doesn't refuse to run with rails 2.1 and 0.25 got some patches to allow better support for 2.1, so it's not completely "unsupported" from a user perspective. The wiki does list >= 2.2.2 for 0.25 and <= 2.2.2 for 0.24 though. > Will try. I was hoping I could get away with using whatever is in > EPEL; has anybody tested this kind of setup? It's definitely unfortunate that what is in EPEL suffers from this bug. I would love to see either puppet or rails there patched to work around this. I filed https://bugzilla.redhat.com/572722 for this issue but haven't heard anything back from the rails packagers yet. There was a bug in the Puppet Labs redmine about these leaks, but I think it was closed. I need to find that bug again and reopen it. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ A neurosis is a secret you don't know you're keeping. -- Kenneth Tynan pgpFk4mncMrw8.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 0.25.5 - Release Candidate 2 available!
James Turnbull wrote: > Welcome back to the Puppet release cycle for the second outing of > 0.25.5 - release candidate number 2. For thoae using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL-4, EL-5 and Fedora 11 - 13 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The problem is not that the world is full of fools. The problem is that lightning isn't being distributed right. -- Mark Twain pgp4WnAoHJKO1.pgp Description: PGP signature
Re: [Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 0.25.5 - Release Candidate 2 available!
I wrote: > For thoae using Fedora or RHEL/CentOS, I've updated the yum repos at: > > http://tmz.fedorapeople.org/repo/puppet/ > > Packages for EL-4, EL-5 and Fedora 11 - 13 are available for testing. > Add the puppet.repo file from either the epel or fedora directories to > /etc/yum.repos.d to enable. And now there are packages for EL-6 as well, for anyone running the RHEL6 beta. (Might as well test one more piece of software while you're at it. ;) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Damn you all! -- Stewie Griffin pgpGxI9WpKe3E.pgp Description: PGP signature
Re: [Puppet Users] Begining with puppet.
Marley Bacelar wrote:
> I am trying to do my first puppet configuration, already installed the
> puppetserver and client, in this link show my configuration and my puppet
> structure:
>
> http://paste.pocoo.org/show/212227/
Which reads, in part:
> # ls /etc/puppet/ #
> files fileserver.conf manifests modules puppet.conf
>
> # fileserver.conf #
> [files]
> path /etc/puppet/files/
> allow 192.168.0.0/24
So you've got a 'files' mount here.
> # ls /etc/puppet/manifests/classes #
> inittab.pp
>
> # inittab.pp #
> class inittab {
> file {
> "inittab":
> mode => 644, owner => root, group => root,
> ensure => present,
> path => $operatingsystem ?{
> default => "/etc/inittab",
> },
> source => "puppet://$servername/inittab",
> }
>
> }
And your source parameter doesn't use the files mount. You'd want to
use 'puppet://$servername/files/inittab' there.
> # ls /etc/puppet/file #
> inittab
I presume you made a typo there, as the dir should be files, not file.
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
The ultimate result of shielding men from the effects of folly is to
fill the world with fools.
-- Herbert Spencer
pgpztMJR17tPa.pgp
Description: PGP signature
Re: [Puppet Users] ANNOUNCE: Puppet 0.25.5 - Release Candidate 3 available!
James Turnbull wrote: > The release candidate is available at: > > http://puppetlabs.com/downloads/puppet/puppet-0.25.5rc3.tar.gz For thoae using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 11 - 13 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Reason obeys itself; and ignorance does whatever is dictated to it. -- Thomas Paine pgpfUVNe3x0fl.pgp Description: PGP signature
Re: [Puppet Users] Nagios checks
Peter Berghold wrote: > Has anybody out there written a custom check for Nagios to determine > if puppetd and/or puppetmasterd is running? I am considering writing > one if not. FWIW, I've got an overengineered check_puppet and puppetstatus tool at: http://tmz.fedorapeople.org/scripts/puppetstatus/ I have found it necessary to disable puppet for a short time to work on something and not have puppet helpfully undo my work more than a few times. While it's easy to use puppetd --disable to prevent puppet from running, it's also easy to forget to re-enable it. Or worse, in a place with multiple SA's, it's easy for someone else to come along and notice puppetd seems to be 'stuck' and 'helpfully' clear out the lock file. Using 'sudo puppetstatus -d "Testing some foo"' creates the lock file as puppetd --disable would, but adds the text given and the username of the person disabling puppet. That then shows up in nagios and if puppet remains disabled for longer than check_puppet would normally consider a critical amount of time, it remains a warning if there is a reason in the lockfile. That also lets other SA's know puppet is down intentionally so they don't have to bug me or worry about 'fixing' it. (The checks in the script to chide folks running it as root are more of a goof, to gently prod admins in the habit of doing everything as root to stop that. :) (Oh, and this is in python -- sorry to any ruby lover's who might take offense. I'll try to turn a blind eye to gems and vendor/ dirs if you don't complain to much about my python usage.) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ All of us could take a lesson from the weather. It pays no attention to criticism. pgpABe5qMfujN.pgp Description: PGP signature
Re: [Puppet Users] Managing RPM Repositories
Matt Wallace wrote:
> I've updated my manifests to reflect the above, however now when I run
> Yum manually on the servers I get the following output:
>
> Repository 'epel' is missing name in configuration, using id
>
>
> It doesn't make a difference to the install, I'm just wondering if I'm
> missing a flag from the following:
>
> yumrepo{epel:
> name => "Epel",
> baseurl=> "http://updates.the.namesco.net/centos\$releasever-\
> $basearch/RPMS.epel/",
> gpgcheck=> "1",
> gpgkey=> "http://download.fedora.redhat.com/pub/epel/RPM-GPG-KEY-EPEL";,
> enabled=> "1",
> includepkgs=> "puppet* ruby* facter augeas-libs ruby-augeas ruby-shadow
> munin-common munin-node munin-server pyparsing libvirt* libyaml* PyYAML*
> cobbler* Django* python-netaddr",
> }
You should set the descr parameter. From the yumrepo docs:
descr
A human readable description of the repository. This corresponds
to the name parameter in yum.conf(5). Set this to ‘absent’ to
remove it from the file completely Valid values are absent. Values
can match /.*/.
So rather than name => "Epel", use descr => "Epel" and should be be
good. (Though a pedant would tell you to spell it as EPEL. ;)
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Fleas can be taught nearly anything that a Congressman can.
-- Mark Twain
pgpg7PkxG1I6b.pgp
Description: PGP signature
Re: [Puppet Users] Re: authenticating new nodes that are created by provisioning
Oded wrote: > Never tried it myself but I think you can create the certificate as > a part of the provisioning process, and then somehow place it in the > new server. > http://serverfault.com/questions/19462/how-can-i-pre-sign-puppet-certificates Without reading the link to see if it's similar to what I do, I have a script I run on the puppet master to pre-generate certificates and package them as rpm's. These then go into a repository which the install is setup to use and the certificate package is installed by kickstart. The package, if you're curious is at: http://tmz.fedorapeople.org/packages/puppet-host-package-0.6.0-1.el5.src.rpm It's not polished in any way. It's one of those "works for me, someday I should finish and improve it" things. But I prefer this to enabling autosign. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The man who can make hard things easy is the educator -- Ralph Waldo Emerson pgpbl0azbCADQ.pgp Description: PGP signature
Re: [Puppet Users] Separate install for just client code?
Forrie wrote: > Is there a way to just install the client component of the Puppet gem, > install of both on systems that don't need the server/master > component. I don't think so. But all decent puppet packages have this separation. I'd highly recommend not using gems. :) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The power of accurate observation is frequently called cynicism by those who don't have it. -- George Bernard Shaw pgpYR21k01xWx.pgp Description: PGP signature
Re: [Puppet Users] strange string in /etc/shadow
Gus F. wrote: > I am using puppet (version 0.25.5-1.e15 for redhat) for password > management for non-system users. This morning, users on some of my > puppet clients had their encrypted password strings in /etc/shadow > replaced with the following string: > > YAML::syck::BadAlias Eeeww. That's no damn good. > That has effectively broken the users' ability to login to those > servers. Puppet will not overwrite that string with the correct > encrypted string, and I can't even change the password manually > using 'passwd', because I get an 'Authentication token manipulation > error'. The only way I can fix this is by manually editing > /etc/shadow, replaced that YAML string with something valid (I've > been using an '*'), and then changing the password manually or > letting puppet overwrite it with the correct password. > > What could have caused this? If you run puppet again, does it attempt to change the entries back? You could run it with --noop to test quickly without risking a change. Though depending on the cause, it might not show up unless you run it without --noop. If no one else chimes in with better ideas, you might want to run "puppetd --test --trace --debug" (after backing up /etc/shadow). Maybe that would help determine the source of the problem. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ I do not believe in the collective wisdom of individual ignorance. -- Thomas Carlyle pgpzPF7lB7Cfk.pgp Description: PGP signature
Re: [Puppet Users] Re: Separate install for just client code?
Forrie wrote: > What is the disadvantage of using the puppet gem vs. installing from > source (install.rb)? Well, I wouldn't recommend that either. I much prefer a proper packaging system like dpkg or rpm. But that's just my opinion. :) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Chemistry is applied theology. -- Augustus Owsley Stanley pgpprQXHTIscg.pgp Description: PGP signature
Re: [Puppet Users] nagios client check?
Daniel Wittenberg wrote: > Anyone written a check for nagios to make sure their nodes are > checking in and updating correctly? I think I'd rather have a > passive check on the nagios server that just alerts me if something > hasn't checked in for last 24 hours rather than having antoher > dashboard to go look at. Anyone tried this? There was a thread on this very subject a few weeks back: http://groups.google.com/group/puppet-users/browse_thread/thread/ab9cb64b3356cba7 :) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ There's no trick to being a humorist when you have the whole government working for you. -- Will Rogers. pgpbd77Uw6l1s.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.0 - Release Candidate 2 available!
James Turnbull wrote: > Welcome back again to the Puppet release cycle with the long-awaited > eleventy times better RC2 release. > > The 2.6.0 release is a major feature release and includes a huge > variety of new features, fixes, updates and enhancements. These > include the complete cut-over from XMLRPC to the REST API, numerous > language enhancements, a complete rewrite of the events and > reporting system, an internal Ruby DSL, a single binary, Windows > support, a new HTTP report processor, and a myriad of other > enhancements. > > As a result of the bucket-load of new features and enhancements we > also need lots of help testing it. Please run up the release > candidate in your test environment or using VMs and test it as > extensively as possible. For thoae using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 12 - 13 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine and help make 2.6.0 as solid as possible for everyone: http://projects.puppetlabs.com/projects/puppet/issues Thanks to everyone who contributed code (from Puppet Labs and elsewhere) for all these cool new features and improvements! -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Politicians are interested in people. Not that this is always a virtue. Fleas are interested in dogs. -- P.J. O'Rourke pgpzK0UqeKJuW.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.0 - Release Candidate 3 available!
James Turnbull wrote: > Welcome back again to the Puppet release cycle with the just out of > the gate release candidate 3. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 12 - 13 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine and help make 2.6.0 as solid as possible for everyone: http://projects.puppetlabs.com/projects/puppet/issues -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Quitters never win, winners never quit, but those who never win AND never quit are idiots. -- Demotivators (www.despair.com) pgpFpKJXSnwSR.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.0 - Release Candidate 4 available!
James Turnbull wrote: > Welcome back again to the Puppet release cycle with really truly > next to final release candidate 4. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 12 - 13 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine and help make 2.6.0 as solid as possible for everyone: http://projects.puppetlabs.com/projects/puppet/issues -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ ...know that worrying is as effective as trying to solve an algebra equation by chewing bubble gum. -- Kurt Vonnegut pgpPWFLzxXBnP.pgp Description: PGP signature
Re: [Puppet Users] Puppet 2.6 Installation
Douglas Garstang wrote: > I just grabbed puppet 2.6, and I'm wondering if there's a way to > install it to an alternative root location. The docs at > http://docs.puppetlabs.com/guides/installation.html talk about how to > set an alternate binary path etc, but nothing about specifying an > alternative root location for all of it. I know this is probably a > ruby question. > > I want to be able to wrap this in an rpmbuild process, which means > specifying a different root install location, you know, for those that > have to install this on a production system. Why not take a look at the existing spec file included in the puppet package, since we do just that? The parameter you're looking for is --destdir. The spec I am referring to is conf/redhat/puppet.spec. Or, for one that is updated for 2.6.0 (very minor changes versus what is in the tarball), see: http://tmz.fedorapeople.org/repo/puppet/epel/5/SRPMS/puppet-2.6.0-0.7.el5.src.rpm -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Start every day with a smile and get it over with. -- W.C. Fields pgpnK2XJXTUnQ.pgp Description: PGP signature
Re: [Puppet Users] Failing to install Packages
Douglas Garstang wrote:
> After going through some dependency hell trying to get the
> rpmforge-release package installed before the RPMforge repo, which
> contains the GPG key for RPMforge packages, now I find that when
> puppet tries to install this package, this happens:
>
> Jul 20 10:20:04 slog01 puppetd[2753]:
> (//yum::client/Package[rpmforge-release]/ensure) change from absent to
> present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install
> rpmforge-release' returned 1: warning: rpmts_HdrFromFdno: Header V3
> DSA signature: NOKEY, key ID 6b8d79e6
>
> The package actually installs, but since it's flagging a warning, and
> it's exit code is 1, AND just about everything else relies on this
> repository being there, puppet fails everything else after it. It
> would be really nice if puppet could ignore the warnings. Now I need
> to find a way to install this rpm outside of puppet, probably in the
> %post section of the kickstart.
You may need to install the gpg key for the the rpmfoge-release
package first. That might be something like:
exec { 'install-rpmforge-gpg-key':
# http URL's work too, but would't be as secure as veryfying the key first.
command => 'rpm --import /path/to/rpmforge-key',
unless => 'rpm -q --quiet gpg-pubkey-6b8d79e6',
}
package { 'rpmforge-release':
ensure => installed,
require => Exec['install-rpmforge-gpg-key'],
}
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Those who have been intoxicated with power... can never willingly
abandon it.
-- Edmund Burke
pgpCGkmAZEWt1.pgp
Description: PGP signature
Re: [Puppet Users] Re: Multiple repositories under one file
CraftyTech wrote:
> Gotcha... and I may also not mind creating multiple files under the
> repo directory, but how do I disable the default repos that come
> with CentOS?
yumrepo { 'base': enabled => 0 }
You can use 'enabled => absent' to remove the repo definition from the
file entirely.
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Tell a man there are 300 billion stars in the universe, he'll believe
you. Tell him a bench has wet paint on it and he'll have to touch it
to be sure.
pgpexTkuZqbPN.pgp
Description: PGP signature
Re: [Puppet Users] Re: Wrong version in SPEC file
Douglas Garstang wrote: > The spec file for for (whatever version this actually is), doesn't > cleanly build an RPM either. > > + /usr/lib/rpm/find-debuginfo.sh /usr/src/redhat/BUILD/puppet-2.6.0 > find: debug: No such file or directory > + /usr/lib/rpm/redhat/brp-compress > + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip > + /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump > + /usr/lib/rpm/brp-python-bytecompile > + /usr/lib/rpm/redhat/brp-java-repack-jars > error: Bad file: /usr/src/redhat/SOURCES/rundir-perms.patch: No such > file or directory > error: Bad file: /usr/src/redhat/SOURCES/puppet-2.6.0.tar.gz.sign: No > such file or directory > > There's nothing on the download page about those two files. Where do I > get them? I don't know what the earlier find error is about. Any reason to not use the packages from: http://tmz.fedorapeople.org/repo/puppet/epel/ The spec file included in the tarballs is not automatically synced up with each relesae, it's there simply as a convenience for folks that don't want to have to rewrite it from scratch. Personally, until 2.6.x is beat on a little more, we probably won't push it into EPEL. But until then, I plan to update my fedorapeople repo with the latest releases and release candidates. You could grab the yum repo file from there and then install puppet-2.6.0 explicitly if you don't want to run 2.6.1rc1. Or, grab the srpm and rebuild it if you like. You'll need to pass in some definitions that the Fedora/EPEL build system uses. rpmbuild --rebuild --define 'dist .el5' --define 'rhel 5' \ --define 'el5 1' /path/to/puppet*.src.rpm You can pass some options to disable augeas and selinux if you like as well. Also, from the /usr/src/redhat paths in your output, it looks like you're building as root. That's generally not a good idea. If you're on RHEL/CentOS, install rpmdevtools and run rpmdev-setuptree to setup a local user account for building. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Marriages are made in heaven. But so are thunder, lightning, and hail. pgpvV4j9WcmfJ.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Facter 1.5.8rc2
James Turnbull wrote: > For 40 days and 40 nights Facter wandered in the wilderness sustained > only by the occasional patch and bottle of Kool-Aid. > > Slightly less tanned and equally happy Facter 1.5.8rc2 has followed rc1 > out of the desert. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 12 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/facter/issues -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ My comment was that the FBI is either incompetent or lying, or both... -- Bruce Schneier, of Counterpane Internet Security, on FBI claims that they don't have specialised machines that can break DES pgpDlv7BZOHXB.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.1 - Release Candidate 3 available!
James Turnbull wrote: > In the long Puppet tradition of fast releases and agile iteration > comes the 2.6.1 release! > > The third release candidate is now available and is a maintenance > release in the 2.6.x branch. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 12 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues (These and the facter packages have been there for a few days, but I figure it's been a little while since I plugged these repos here and not everyone may know about them.) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ To be stupid, selfish, and have good health are three requirements for happiness, though if stupidity is lacking, all is lost. -- Gustave Flaubert pgp2xKuK6nBnm.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Facter 1.5.8
James Turnbull wrote: > For 40 days and 40 nights Facter wandered in the wilderness > sustained only by the occasional patch and bottle of Kool-Aid. > > Slightly less tanned and equally happy Facter 1.5.8 has arrived! :) > 1.5.8 is a feature and maintenance release containing a number of > fixes, updates and additional tests. Congratulations on sheparding facter through another release cycle. Look for it in Fedora and EPEL testing repositories soon. Fedora and/or EPEL users are encouraged to test and provide feedback at https://admin.fedoraproject.org/updates/facter when these updates are pushed. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ As long as people will accept crap, it will be financially profitable to dispense it. -- Dick Cavett, in "Playboy", 1971 pgpHvXUOSMrLe.pgp Description: PGP signature
Re: [Puppet Users] Puppet 2.6.1rc2 does not honor agent's --tags option
Jean-Baptiste Quenot wrote: > After upgrading Puppet from 0.24.8 to 2.6.1rc2 at my company, I > notice that puppet agent's --tags option is not honored anymore: Did you happen to file a ticket for this yet? I need to test more myself, but I believe I saw this the other day too, with rc3. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Years ago fairy tales all began with "Once upon a time...", now we know they all begin with, "If I am elected..." -- Carolyn Warner pgpLRW6aim9zA.pgp Description: PGP signature
Re: [Puppet Users] [puppet-server] - "/var/lib/puppet" while installing 0.25.5 puppet-server
Patrick wrote: > I would assume that the package maintainer moved the default > directory location. The Fedora/EPEL packages don't change this. I'm not sure if there are any other yum using distros out there. But if the OP meant one of those two, then /var/lib/puppet is the default $vardir. There's just nothing installed there by the packages. Running puppet will create whatever files and dirs are needed there. > Try this: > puppetmaster --genconfig | grep "libdir =" I think you mean: puppetmasterd --genconfig | grep "vardir =" (Note the d on the end of puppetmaster and s/libdir/vardir :) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ A common mistake people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. -- Douglas Adams pgpIUwUjDU1AN.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.1 released!
James Turnbull wrote: > In the long Puppet tradition of fast releases and agile iteration > comes the 2.6.1 release! For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 12 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I'm particularly interested in anyone updating from 0.25.x to 2.6.x and whether you run into regressions or other issues that would make this an unsuitable update to push into the stable Fedora and EPEL repositories. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Thieves respect property. They merely wish the property to become their property that they may more perfectly respect it. -- G. K. Chesterton, "The Man Who Was Thursday", 1908 pgpDfxln4Nbwk.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] GitHub Account move - the Great Migration continues...
James Turnbull wrote: > For example the Puppet respository that would have been cloned like: > > $ git clone git://github.com/reductivelabs/puppet.git > > Should now be cloned like: > > $ git clone git://github.com/puppetlabs/puppet.git I know this came up in IRC the other day, so for anyone with a current clone that wants to ensure it is pulling from the properl location, there are numerous ways to do so. If you have git >= 1.7.0, you can use: $ git remote set-url origin git://github.com/puppetlabs/puppet.git Otherwise, you can use git config: $ git config remote.origin.url git://github.com/puppetlabs/puppet.git Or, you can just edit .git/config directly and set the url parameter appropriately. (If you go this route, you've likely been using git since long before it had convenient commands to manage settings. That, or you're just hard-core about the *nix way. :) Hope this helps, -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Einstein argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer. -- Fred Brooks pgpyYgV6ya9S7.pgp Description: PGP signature
Re: [Puppet Users] Small bug: puppet.spec still refers to 2.6.0
Nigel Kersten wrote: > On Tue, Sep 14, 2010 at 3:51 PM, Douglas Garstang >> Lets play rock paper scissors to see who files a bug... > > That's uncharitable and unfair. Indeed. I usually joke that all complaints should be submitted in unified diff format. I actually feel bad anytime I file a bug without a patch. > The package maintainers are responsible for their packages. > The spec file was in the upstream source as a convenience to make it > easier for people to rebuild packages themselves, but the maintainers > are still responsible for the package and spec files. I think it might be reasonable to have a rake task to help automate creating packages for various systems. But I've never spent the time to try and implement that, so I'm in no position to say that's how it should be. Doing it well would be nice, but more involved than a few lines of code. I think you'd want to default to detecting the current OS and version (via facter, naturally) but perhaps allow for building against other versions (or even similar OS's, like building for RHEL/CentOS on a Fedora host). That gets messy quickly. I'm not sure what's so wrong with grabbing the packages provided for various distros/OS's really. I know for Fedora and RHEL/CentOS I try to keep my personal repository updated quickly and/or have the packages in the official repositories. For Debian/Ubuntu, building from a git clone is fairly easy (makes me a tad jealous even :). Around the time of new releases, we (as in Fedora/EPEL maintainers) usually don't push updates into the official repositories as quickly, in order to let the early adopters help flush out unintended regressions or changes in behavior. I think it's reasonable to expect that folks following this list and eager for the very latest packages either know where they can get them or are capable of building them on their own -- if s/2.6.0/2.6.1, screws anyone, they shouldn't be building their own packages in the first place ;). I can try to submit the trivial patch to change the version from 2.6.0 to 2.6.1, but really, if we're going to keep the rpm spec files in the tarball, someone that cares deeply (i.e. someone that has the balls to bitch about it on the list and not be willing to file a bug) should work on a patch to make this happen more automatically. That way when James does a release it just works, and doesn't add more work to all that he and many other folks already do to prepare, test, and push a new release. In the interim, you're welcome to use the packages (binary and/or source) that I've prepared for Fedora and RHEL/CentOS: http://tmz.fedorapeople.org/repo/puppet/ (Note that I provide these packages without warranty, and while I'm grateful for any testing and reports of packaging issues, I'm not at all likely to respond quickly or kindly anyone demanding any sort of support from me for them.) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ I personally think we developed language because of our deep need to complain. -- Lily Tomlin pgpI1DhBC6EFK.pgp Description: PGP signature
Re: [Puppet Users] Re: Wrong version in SPEC file
micha...@tnrglobal.com wrote: > On Sep 16, 4:23 pm, "R.I.Pienaar" wrote: >> rpmbuild -ba -D 'dist .el5' -D 'rhel 5' -D '_without_augeas 1' puppet.spec > > Great- that works. I also just tried: > rpmbuild --without augeas --without selinux --rebuild > puppet-2.6.1-0.5.el5.src.rpm FWIW, the spec file has this at the very top: # Augeas and SELinux requirements may be disabled at build time by passing # --without augeas and/or --without selinux to rpmbuild or mock For any non-ancient rpm, that should work as well as the -D syntax above. (RHEL4 rpm qualifies as ancient and isn't something I test with very often.) Also note that the rpmbuild command you used above, without the -D 'dist .el5' -D 'rhel 5' would lack requirements on ruby(abi) = 1.8 and ruby-shadow and would not build noarch packages. Both of those things depending on those macros being set (as they are on the EPEL build system). In fact, lacking those macros will cause augeas and selinux to not be required either, irregardless of setting --without augeas or selinux. If you rebuild a lot of packages from Fedora or EPEL on RHEL/CentOS systems, you may want to use mock for building or install the buildsys-macros package which provides these common macros: http://buildsys.fedoraproject.org/buildgroups/rhel5/x86_64/buildsys-macros-5-5.el5.noarch.rpm On all supported Fedora releases, these macros are defined as part of the stock install. I believe that's the case for RHEL6 too, but I don't have access to any RHEL6 beta systems at the moment to verify that. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ There are no stupid questions, but there are a LOT of inquisitive idiots. -- Demotivators (www.despair.com) pgpsMp4DXHNmT.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.2 released!
James Turnbull wrote: > And we're back with another exiting release in the 2.6.x branch - > 2.6.2. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 12 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I'm particularly interested in anyone updating from 0.25.x to 2.6.x and whether you run into regressions or other issues that would make this an unsuitable update to push into the stable Fedora and EPEL repositories. (And for those still reading and thinking that someone else will test and provide feedback, let me say that I've had none so far. For all I know, no one has updated from 0.25.5 to 2.6.2 on Fedora/EPEL using these packages. :) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ How can I tell that the past isn't a fiction designed to account for the discrepancy between my immediate physical sensation and my state of mind? -- Douglas Adams pgpbPqKQoNTyb.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet Dashboard 1.0.4 Release Candidate 2!
James Turnbull wrote: > You can install the RPM package for CentOS or RHEL 5.5 by running the > following from your shell: > sudo sh -c "rpm -Uvh > http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm; > \ > cd /tmp/ \ > && wget -c > http://www.puppetlabs.com/downloads/dashboard/puppet-dashboard-1.0.4rc2-1.noarch.rpm > \ > && gpg --keyserver x-hkp://pgp.mit.edu --recv-keys 4bd6ec30 \ > && gpg --armor --export 4bd6ec30 > /tmp/puppetlabs.asc \ > && rpm --import /tmp/puppetlabs.asc \ FWIW, you could simplify this to: rpm --import http://yum.puppetlabs.com/RPM-GPG-KEY-puppetlabs (Or an https URL for better security.) Sadly, yum on EL-5 is a bit too old to know how to install directly from an http URL. In Fedora, that's possible. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ So I don't get hurt?! That's the best you can come up with you dull-witted termagant! -- Stewie Griffin, on why he needs a car seat pgpqr8Dz4lcB2.pgp Description: PGP signature
Re: [Puppet Users] Re: ANNOUNCE: Puppet 2.6.2 released!
Chuck wrote: > I have migrated my EL5 servers from 0.25.5 to 2.6.2 and have no > issues now. I did have some issues with 2.6.1 which are now fixed. > I would like to see 2.6.2 in the official EPEL repository. Thanks for the feedback Chuck! Were any changes to your config or manifests required (aside from changes to silence deprecation warnings)? -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Many a person seems to think it isn't enough for the government to guarantee him the pursuit of happiness. He insists it also run interference for him. -- Anonymous pgpGJSpDBVBNZ.pgp Description: PGP signature
Re: [Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.2 released!
Ben wrote: > I did a server and all client upgrade to your 2.6.1 package from > your 0.25.5 package without any problems w/ your packaging. > Install, init scripts, etc all work fine. > > And now the upgrade to 2.6.2 looks good after 5 whole minutes. > > Server: CentOS 5.5 > Clients: CentOS 5.x, RHEL 5.x, Fedora 8 and 13. > > My only issues were some syntax in my manifests that 2.6.1 didn't > like, but 0.25.5 silently ignored and a significant increase in > compile times. Thanks Ben! Were the changes to your manifests required to get puppet to run at all or just do silence new or deprecation warnings? -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Excess on occasion is exhilarating. It prevents moderation from acquiring the deadening effect of a habit. -- W. Somerset Maugham pgpckXAR9YnRP.pgp Description: PGP signature
[Puppet Users] Re: ANNOUNCE: Puppet 2.6.3 - Release Candidate 1 available!
James Turnbull wrote: > All too quickly we're back with a maintenance release: 2.6.3. This > release addresses some issues in the 2.6.2 release. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 12 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I'm particularly interested in anyone updating from 0.25.x to 2.6.x and whether you run into regressions or other issues that would make this an unsuitable update to push into the stable Fedora and EPEL repositories. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ I personally think we developed language because of our deep need to complain. -- Lily Tomlin pgpoDnWnNLVlv.pgp Description: PGP signature
Re: [Puppet Users] First boot with Puppet
Steven VanDevender wrote: > I'm not our local Cobbler/Kickstart expert, but the guy who created > our Cobbler installation even figured out how to script a new host's > initial registration with the puppetmaster (I believe the key idea > is that there is a command-locked ssh identity key that allows the > host to get in to the puppetmaster and issue the right "puppetca" > command). I'd have to do some digging to look up the specifics. I handle this in my environment by generate the new host key on the puppetmaster and packaging that into an rpm, which gets installed in the kickstart along with puppet. That way an initial puppet run can happen during install. Doesn't exactly scale, unless you automate the key generation though, like you mentioned doing. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ There are severe limits to the good that the government can do for the economy, but there are almost no limits to the harm it can do. -- Milton Friedman. Nobel laureate pgpjSQTb3suHT.pgp Description: PGP signature
Re: [Puppet Users] Upgrade to 2.6: Cannot use class name as tag anymore?
Daniel Kerwin wrote: > i just upgraded some servers to Puppet 2.6.2 and it seems like it's > not possible to use class names as tags anymore. I haven't found any > documentation about this except a bug for 2.6.1 that should be fixed > (http://projects.puppetlabs.com/issues/4631). > # ~ # puppet agent --test --noop --tags main::firewall Have you tried using just --tags firewall? I've never tested with main:: prefixed. But using the classname works for me with 2.6.3rc1. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Unquestionably, there is progress. The average American now pays out twice as much in taxes as he formerly got in wages. -- H. L. Mencken pgpjWqIpkzbrU.pgp Description: PGP signature
Re: [Puppet Users] Re: Installing Software via Puppet
Maciej Skrzetuski wrote: > Do you mean hosting your own yum repository in your own network? > That is not a bad idea but it would be easier to just copy the files > over to the puppets and then just rpm -ihv , wouldn't it? No, it wouldn't be. You lose yum's ability to install depndencies for one. Creating a yum repository is as simple as "createrepo /path/" and serving that via apache really. > Another question in this context is: How can I install software (for > example RPMs) on all my puppets only on demand? Can you tell puppet > to install s.th. right "now"? Puppet's not really geared to that sort of one-off thing. Tools like func or mcollective are better suited for that. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ I am not young enough to know everything. -- Oscar Wilde (1854-1900) pgp4WGbNLVCI9.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.3 - Release Candidate 2 available!
James Turnbull wrote: > We're back with a maintenance release: 2.6.3. This > release addresses some issues in the 2.6.2 release. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 12 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I'm particularly interested in anyone updating from 0.25.x to 2.6.x and whether you run into regressions or other issues that would make this an unsuitable update to push into the stable Fedora and EPEL repositories. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ What George Washington did for us was to throw out the British, so that we wouldn't have a fat, insensitive government running our country. Nice try anyway, George. -- D.J. on KSFO/KYA pgpufA9h1iAwn.pgp Description: PGP signature
Re: [Puppet Users] ANNOUNCE: Puppet 2.6.3 - Release Candidate 3 available!
James Turnbull wrote: > We're back with a maintenance release: 2.6.3. This > release addresses some issues in the 2.6.2 release. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 12 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I'm particularly interested in anyone updating from 0.25.x to 2.6.x and whether you run into regressions or other issues that would make this an unsuitable update to push into the stable Fedora and EPEL repositories. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The worst thing about history is that every time it repeats itself, the price goes up. -- Pillar pgpKXIrbzIb9q.pgp Description: PGP signature
[Puppet Users] Re: ANNOUNCE: Puppet 2.6.3 released!
James Turnbull wrote: > We're back with a new release: 2.6.3. This > release addresses some issues in the 2.6.2 release. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 12 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I'm particularly interested in anyone updating from 0.25.x to 2.6.x and whether you run into regressions or other issues that would make this an unsuitable update to push into the stable Fedora and EPEL repositories. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The direct use of physical force is so poor a solution to the problem of limited resources that it is commonly employed only by small children and great nations. -- David Friedman pgpii7ACyzeC8.pgp Description: PGP signature
Re: [Puppet Users] 2.6.x Ruby DSL
Nick wrote: > RHEL/CentOS 5 has nothing at all in base, and only v22.4 in RPMForge You want to use EPEL for puppet in RHEL/CentOS, as the RPMForge packages are way out of date. That said, we've stuck with 0.25.5 for now in EPEL. But I have 2.6.x builds in my own repository to aid in testing on RHEL/CentOS. Ideally, that will help early adopters shake out any remaining bugs/regressions in 2.6.x and clear the way for us to make a seemless update in EPEL before too long. Please yell if you find nasty surprises upon updating to the 2.6.x packages at: http://tmz.fedorapeople.org/repo/puppet/ -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ I need not suffer in silence while I can still moan, whimper, and complain. pgpF3CtKhD4yj.pgp Description: PGP signature
Re: [Puppet Users] ANNOUNCE: Puppet 2.6.4 released!
James Turnbull wrote: > Due to a security issue (see recent SECURITY email) we're releasing a > 2.6.4 release immediately. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I'm particularly interested in anyone updating from 0.25.x to 2.6.x and whether you run into regressions or other issues that would make this an unsuitable update to push into the stable Fedora and EPEL repositories. (Yes, I know the 2.6.x packages I've previously provided aren't vulnerable to this issue. But this way no one has to guess based on the version number. ;) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ First, God created idiots. That was just for practice. Then He created school boards. -- Mark Twain pgpQ7QotUvUwI.pgp Description: PGP signature
Re: [Puppet Users] tmz repo
Arnau Bria wrote: > maybe it's a little OT... anyone knows if old puppet version from tmz > repos are still available somewhere? I have some of them locally. I clean out older versions to conserve space on my fedorapeople.org account. Were you looking for a particular previous version? -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Between two evils, I always pick the one I never tried before. -- Mae West pgpSPj1rxmtfo.pgp Description: PGP signature
Re: [Puppet Users] Re: puppet 2.6.4 installation options for redhat/centos
pzi wrote: > Just as I said if I have a choice of using tar file from the source > I will always favor it over rpms cooked in unknown environment. Just FYI, the packages in my repo are built in the Fedora/EPEL buildsystem. They're signed with the same GPG key I use for my mail as well. Not that you should trust me. But then, if you don't, just know that I can as easily slip a trojan into my personal repository as I can into the EPEL packages -- if I were that sort of miscreant. :) Also, it should be pretty simple to build your own rpm packages from the spec file in the tarball or from the srpm in my repository (the process has been documented numerous times on this list). Any of those is preferable to installing directly from a tarball. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Nothing is so permanent as a temporary government program. -- Dr. Milton Friedman, Nobel-Prize-winning economist. pgpVEWjczmrTs.pgp Description: PGP signature
Re: [Puppet Users] puppet 2.6.4 installation options for redhat/centos
sstein...@gmail.com wrote: > FWIW, I just went through the same annoyance, slightly different > issues on Ubuntu 10.04, it's not just Red Hat/Cent OS that's way out > of date. It's always tricky to keep up with a relatively young and fast moving project like puppet -- especially if you don't want to make end users fear running a simple 'yum update' (or apt, etc.). If every update was guaranteed not to break anyone's currently working manifests, I'd happily roll out puppet updates in EPEL much more often. But that's not an easy task. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ It is impossible to enjoy idling thoroughly unless one has plenty of work to do. -- Jerome K. Jerome pgpdvNRcuj5te.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.5 - Release Candidate 1 available!
Nick Lewis wrote: > We're back with a maintenance release: 2.6.5. This > release addresses a number of bugs in the 2.6.x branch. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I'm particularly interested in anyone updating from 0.25.x to 2.6.x and whether you run into regressions or other issues that would make this an unsuitable update to push into the stable Fedora and EPEL repositories. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Common sense is the collection of prejudices acquired by age eighteen. -- Albert Einstein pgpXT0yWwjF3f.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.5 - Release Candidate 2 available!
Jacob Helwig wrote: > We're back with a maintenance release: 2.6.5. This release addresses a > number of bugs in the 2.6.x branch and adds a handful of features and > documentation updates. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I'm particularly interested in anyone updating from 0.25.x to 2.6.x and whether you run into regressions or other issues that would make this an unsuitable update to push into the stable Fedora and EPEL repositories. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Optimist, n.: A proponent of the doctrine that black is white. -- Ambrose Bierce, "The Devil's Dictionary" pgp0jsHLjY8GN.pgp Description: PGP signature
[Puppet Users] Re: ANNOUNCE: Puppet 2.6.5 - Release Candidate 4 available!
Jacob Helwig wrote: > We're back with a maintenance release: 2.6.5. This release addresses a > number of bugs in the 2.6.x branch and adds a handful of features and > documentation updates. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I'm particularly interested in anyone updating from 0.25.x to 2.6.x and whether you run into regressions or other issues that would make this an unsuitable update to push into the stable Fedora and EPEL repositories. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Whenever you find yourself on the side of the majority, it is time to pause and reflect. -- Mark Twain pgpInubhW8oaP.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.5 - Release Candidate 5 available!
Paul Berry wrote: > We're back with a maintenance release: 2.6.5. This release addresses > a number of bugs in the 2.6.x branch and adds a handful of features > and documentation updates. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 14 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I'm particularly interested in anyone updating from 0.25.x to 2.6.x and whether you run into regressions or other issues that would make this an unsuitable update to push into the stable Fedora and EPEL repositories. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ I cook with wine, sometimes I even add it to the food. -- W.C. Fields pgpQM9AC6DiGS.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.5 released!
Nigel Kersten wrote: > The release is available for download at: > > http://puppetlabs.com/downloads/puppet/puppet-2.6.5.tar.gz Congratulations and thanks to all the folks who worked on the release! For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I plan to get these packages built for Fedora and EPEL testing repositories in the next few days. Anyone who finds showstopper bugs before then will be my hero for the day. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The problem with politics isn't the money; it's the power. -- Harry Browne pgpLK0DHQ5snA.pgp Description: PGP signature
Re: [Puppet Users] Re: best way of handling source installs
russell.fulton wrote: > I'll repeat the question from my previous post: Is there a straight > forward way to have a local rpm repository on the puppet server > rather than relying on yum and the RHE channels? It's trivial to run createrepo /path/to/rpms to create the yum metadata. You can then serve that up via http or even via a file:// URI if you like (and your clients can access it). Or are you trying to get puppet to act as the repository? If so, I don't think there is a sane way to do this. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ You cannot propel yourself forward by patting yourself on the back. pgp6qAAyj78x3.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.6 - Release Candidate 1 available!
Jacob Helwig wrote: > This maintenance release fixes two issues with Puppet 2.6.5. To help with testing on Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Ambition is a poor excuse for not having enough sense to be lazy. pgpbxDKTzYv8B.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.6 available!
Jacob Helwig wrote: > This maintenance release fixes two issues with Puppet 2.6.5. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I plan to get these packages built for Fedora and EPEL 5/6 testing repositories in the next few days. Anyone who finds showstopper bugs before then will be my hero for the day. (Thomas, you beat me. That'll teach me to drink on the beach at sunset, damn it. ;) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ If the triangles were to make a God they would give him three sides. -- Montesquieu pgpSi8bM5F4Xr.pgp Description: PGP signature
[Puppet Users] Re: ANNOUNCE: Facter 1.5.9rc2
Jacob Helwig wrote: > Facter 1.5.9rc2 is a maintenance release containing fixes and updates. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/facter/issues -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Nothing in education is so astonishing as the amount of ignorance it accumulates in the form of inert facts. --Henry Brooks Adams pgpwCXnkHBIMa.pgp Description: PGP signature
Re: [Puppet Users] Re: ANNOUNCE: Puppet 2.6.6 available!
Hi T.J., T.J. Yang wrote: > I looked at puppet 2.6.6-0.5 puppet client and server packages. > Two questions so far about the client(R1) /server(R2) packaging. > > 1. why puppetca reside in client rpm but not in server rpm ? While I don't speak for Jeff or the Puppet Labs folks, the packages there are substantially the same as what has developed from Fedora/EPEL (which eventually ends up in conf/redhat/puppet.spec when I'm not too much of a slacker to file a ticket and be a good contributor). In Fedora/EPEL, we moved puppetca into the main puppet package back in 0.25.1rc1, as there was some discussion on the list or in IRC about it. There are times when you may want to use puppetca a system other than the master, thus it's in the main puppet package. > 2. shouldn't client and server each has their own /etc/logrotate.d/ > puppet ? It seems redundant to do so, since the logrotate script handles everything in /var/lib/puppet and will condrestart both puppetmaster and puppet as needed. Since puppet-server requires puppet, you'd have to try hard to not have the logrotate script after installing the puppet-server package. BTW, Jeff, there don't seem to be any SRPMS for 2.6.6 in the puppetlabs prosvc repo, for anyone that may want to grab them and rebuild them (or see if there are any differences from the spec file in the tarball or EPEL that should be merged). -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ School is the advertising agency which makes you believe that you need the society as it is. -- Ivan Illich -- "Deschooling Society" pgpdQptjI1gti.pgp Description: PGP signature
[Puppet Users] [PATCH/facter] (#6763) Use Facter::Util::Resolution.exec for arp
The arp command is in /sbin on Fedora/RHEL, not /usr/sbin. Using
Facter::Util::Resolution.exec is preferable to hard-coding the path.
---
lib/facter/arp.rb |8 +---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/lib/facter/arp.rb b/lib/facter/arp.rb
index 65cf4c3..5035ad0 100644
--- a/lib/facter/arp.rb
+++ b/lib/facter/arp.rb
@@ -4,9 +4,11 @@ Facter.add(:arp) do
confine :kernel => :linux
setcode do
arp = []
-output = %x{/usr/sbin/arp -a}
-output.each_line do |s|
- arp.push($1) if s =~ /^\S+\s\S+\s\S+\s(\S+)\s\S+\s\S+\s\S+$/
+output = Facter::Util::Resolution.exec('arp -a')
+if not output.nil?
+ output.each_line do |s|
+arp.push($1) if s =~ /^\S+\s\S+\s\S+\s(\S+)\s\S+\s\S+\s\S+$/
+ end
end
arp[0]
end
--
1.7.4.1
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
In the beginning the Universe was created. This has made a lot of
people very angry and has been widely regarded as a bad move.
-- Douglas Adams
--
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 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: [Puppet-dev] ANNOUNCE: Puppet 2.6.6 available!
I wrote: > I plan to get these packages built for Fedora and EPEL 5/6 testing > repositories in the next few days. Anyone who finds showstopper bugs > before then will be my hero for the day. Puppet 2.6.6 packages are now in Fedora and EPEL testing repositories. Anyone testing these packages is encouraged to leave feedback in the update tool via: https://admin.fedoraproject.org/updates/puppet If you have a Fedora account, you can give the update positive or negative karma. More positive feedback will help get the update into the stable repositories faster. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ If you haven't the strength to impose your own terms upon life, you must accept the terms it offers you. -- T.S. Eliot pgp9GO5ZH8wWC.pgp Description: PGP signature
Re: [Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.6 available!
Hi TJ, TJ Yang wrote: > I am not familiar with yum. Would you mind provide a simple > instruction to enable yum to install your test package ? You must enable the updates-testing repo on Fedora (or epel-testing on RHEL/CentOS). yum --enablerepo updates-testing install puppet -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The problem is not that the world is full of fools. The problem is that lightning isn't being distributed right. -- Mark Twain pgpxvOtF2Pti1.pgp Description: PGP signature
Re: [Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.6 available!
Ben Hughes wrote: > On Sun, Mar 20, 2011 at 01:17:17PM -0500, TJ Yang wrote: > >> I am not familiar with yum. Would you mind provide a simple >> instruction to enable yum to install your test package ? > > http://www.craigdunn.org/2010/08/part-1-installing-puppet-2-6-1-on-centos-with-yumrpm/ > > Covers the basics of using yum to install puppet using tmz's > repository. That post mixes the puppetlabs, epel, and other third-party repos. It doesn't use the repo I have on fedorapeople.org at all that I can see. It also instructs you to create an repo files with gpg checks disabled, which is a completely unnecessary risk to take. Instructions for enabling my fedorapeople repos are in the README file: http://tmz.fedorapeople.org/repo/puppet/README That said, I believe TJ's question was aimed at installing the packages now in the official Fedora and EPEL testing repositories rather than the unofficial packages I maintain at fedorapeople.org. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Some of the narrowest minds are found in the fattest heads. -- Anonymous pgp0chzcPhLnz.pgp Description: PGP signature
Re: [Puppet Users] ANNOUNCE: Facter 1.5.9rc4
Jacob Helwig wrote: > Facter 1.5.9rc4 is a maintenance release containing fixes and updates. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/facter/issues -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ America wasn't founded so that we could all be better. America was founded so we could all be anything we damned well pleased. -- P.J. O'Rourke pgpXrS29QFWWF.pgp Description: PGP signature
Re: [Puppet Users] gpg key errors
Tim Dunphy wrote: > I am having a strange occurrence where I can run puppet on a client > successfully and have it install httpd and php and a few other > packages. The first run everything goes ok and everything installs > perfectly the first run. But if I delete the packages (using yum > remove foo) and run puppet again I get gpg key errors and the packages > fail to install. > > ## puppet errors > > err: /Stage[main]/Apache/Package[php-mcrypt.i386]/ensure: change from > absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y > install php-mcrypt.i386' returned 1: warning: rpmts_HdrFromFdno: > Header V3 DSA signature: NOKEY, key ID cf4c4ff9 > > > Public key for php-mcrypt-5.2.17-1.1.w5.i386.rpm is not installed You need to install the GPG key for the repository that is providing those php packages. Alternately, you could disable gpg checks in the repo file for this repo, but that's not something I'd recommend. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Learn from the mistakes of others--you can never live long enough to make them all yourself. -- John Luther pgp5pJgUSvgVg.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.7 final!
Jacob Helwig wrote: > This release addresses issues with the Puppet 2.6.x series and adds > the Inventory Service. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues Please note that 2.6.6 is in Fedora and EPEL testing repositories. I don't plan to update puppet there until 2.6.6 is pushed to the stable updates repos in a few weeks. Any help testing the 2.6.6 packages is most welcome. Once that update is stable, we'll be better able to more closely track the 2.6.x updates in the official repos. Also worth noting is that I have no plans to update the official EL-4 repos with 2.6. EL-4 is nearing its EOL and such an update seems more likely to cause unneeded pain for little gain. I will keep updating the EL-4 packages in my fedorapeople repos though, for anyone using EL-4 _and_ wanting the latest packages (you poor, confused souls ;). -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The urge to save humanity is almost always a false front for the urge to rule. -- H. L. Mencken pgp2nnFy5tzKw.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Facter 1.5.9rc5
Jacob Helwig wrote: > Facter 1.5.9rc5 is a maintenance release containing fixes and updates. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/facter/issues -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ A penny saved kills your career in government. pgpeXnSvQMDSR.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.8rc1 available!
Matt Robinson wrote: > This release addresses issues with the Puppet 2.6.x series. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues Please note that 2.6.6 is in Fedora and EPEL testing repositories. I don't plan to update puppet there until 2.6.6 is pushed to the stable updates repos. Any help testing the 2.6.6 packages is most welcome. Once that update is stable, we'll be better able to more closely track the 2.6.x updates in the official repos. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Why is it that we rejoice at a birth and grieve at a funeral? It is because we are not the person involved. -- Mark Twain pgpsLnijWfcOp.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: Facter 1.5.9rc6
Nigel Kersten wrote: > Facter 1.5.9rc6 is a maintenance release containing fixes and updates. For those using Fedora or RHEL/CentOS, I've updated the yum repos at: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Every time I close the door on reality, it comes in through the windows. pgpIaeD2IMRAz.pgp Description: PGP signature
Re: [Puppet Users] Re: Puppetmaster leaving files open with "too many files open" error
treydock wrote: > What is the current issue number? The only one I could find that > mentions the same problem is this , > http://projects.puppetlabs.com/issues/7203. https://bugzilla.redhat.com/show_bug.cgi?id=572722 and http://projects.puppetlabs.com/issues/3693 are both relevant here. I'd love to see a fix in either the rails activerecord component or in puppet. Seeing that older puppet versions worked with the rails stack in EPEL, it seems like it should be possible to make that work again with some changes to puppet. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ It is strangely absurd to suppose that a million human beings collected together are not under the same moral laws which bind them separately. -- Thomas Jefferson pgpz0HtzL8gSz.pgp Description: PGP signature
Re: [Puppet Users] Re: Puppetmaster leaving files open with "too many files open" error
Nathan Clemons wrote: > http://projects.puppetlabs.com/issues/3238 is the issue I was > thinking of, but 3693 is probably a duplicate of that. > > These bugs have been open a really long time. Outside of lowering > the MySQL timeout value, are there any workarounds for this problem? > I can't really understand how Zynga can be managing as many hosts > via Puppet as they do without being affected by a bug like this, > unless they're not using stored configs (which would surprise me). Sadly, I don't know of any decent workarounds. I ended up rolling a rails-2.3.5 for EL-5 in the production instances I wanted to use storedconfigs. I would love to see a workaround or a patch for either the activerecord or puppet packages. I know that either way this can be fixed will get into EPEL shortly, as it's a very annoying bug that was introduced with the update from 0.24 to 0.25. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ I figure that if God actually does exist, He's big enough to understand an honest difference of opinion. -- Isaac Asimov pgpUKhQvrpn2A.pgp Description: PGP signature
[Puppet Users] Re: /etc/skel
Rene wrote:
> In our environment, we have a non standard /etc/skel directory. The
> content of that directory is managed via puppet. How do I guarantee,
> that the content of that directory is on the system before a user is
> created. Do I need a require attribute on every user creation
> statement in every puppet module we have? Does someone know an
> easier way?
You could use a resource default to add that requirement to user
resources:
User {
require => File['/etc/skel']
}
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
After one look at this planet any visitor from outer space would say
"I want to see the manager."
-- William S. Burroughs
pgppGJ5xtIt81.pgp
Description: PGP signature
[Puppet Users] Re: Obtaining puppet and facter for RHEL5/Centos5
Trevor Hemsley wrote: > What's the correct yum repo to use for installing Puppet & Facter on > RHEL5 and Centos5? > > I used to get them from the dlutter-rhel5 repo but this seems to be > massively out of date now - latest version of puppet-server in there > is 0.24.5-1.el5 and facter 1.5.4-1.el5. > > In Epel I see puppet-server 0.24.8-1.el5.1 and facter 1.5.4-1.el5 > which is better but isn't 1.5.4 the version that hangs? > > In epel-testing there is no puppet-server but there is a facter > 1.5.5-1.el4 but that sounds like a release for RHEL4 not 5. > > Is there a repo that I am not checking? Generally, the most up to date packages are in epel-testing. If you enable epel-testing, you'll also want epel enabled. At the moment, that will get you the latest stable releases of puppet and facter (well, facter is at 1.5.5 instead of 1.5.6 because 1.5.6 doesn't contain any fixes relevant for Fedora/EPEL). If you really want to live dangerously, I have puppet-0.25beta1 packages in a repo on fedorapeople.org: http://tmz.fedorapeople.org/repo/puppet/epel/ Like Lutter's repo, this one is meant for use only by those willing to test new packages at their own risk. Of course I'm always interested in reports of packaging bugs, but I can't guarantee I'll be able to push out fixed packages in a hurry there. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ I got nasty habits. I take tea at 3. pgpWtAquFwGBv.pgp Description: PGP signature
[Puppet Users] Re: Obtaining puppet and facter for RHEL5/Centos5
Trevor Hemsley wrote: > I have EPEL itself enabled as one of my repos but epel-testing is > generally disabled - enabled only when I need specific things from > it. That works. > Currently epel-testing for RHEL5/CentOS5 appears to have a wrong > package in it for facter (1.5.5-1.el4 vs .el5). I suspect it > probably works anyway but I haven't checked it to find out. Are you sure your repo configs are correct? I don't see a .el4 facter package in the epel-testing repos for EL5: http://download.fedora.redhat.com/pub/epel/testing/5/ -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ To have a successful relationship, I must learn to make it look like I'm giving as much as I'm getting. pgp9DEQn2gaDn.pgp Description: PGP signature
[Puppet Users] Re: Obtaining puppet and facter for RHEL5/Centos5
Trevor Hemsley wrote: > They are correct but they were not before. What I seem to have > discovered that I didn't know before is that `yum clean all` needs to be > told to --enablerepo=epel-testing in order to clean the cache for that > repo (yes, it's documented but only when you bother to look it up :) ) Heh, I saw this just the other day and thought how unintuitive it is. I know I would expect yum clean all to clean, you know, _all_. ;) Anyway, glad that sorts things out for you. If you find any packaging bugs, don't hesitate to report them to us via bugzilla.redhat.com. Or report it here if you're unsure if it's packaging or not. We can certainly help figure out where to report the problem. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Going to hell when I die would just be redundant. pgpYGWOPZ5zFm.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] New RedHat RPMs for puppet 0.24.8 and factor 1.5.5
Ricky Zhou wrote: > puppet-0.24.8-1.el5.1 and facter-1.5.5-1.el5 are available in EPEL > (Extra Packages for Enterprise Linux), if you're using RHEL or CentOS. > In fact, I think the maintainer is on this list :-) Yep, several of us are. And if the latest stable isn't new enough for you, I have 0.25.0beta1 in a personal repo at: http://tmz.fedorapeople.org/repo/puppet/ We also try to keep the spec files updated for the latest stable releases in the facter and puppet sources (conf/redhat/*.spec). -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Between two evils, I always pick the one I never tried before. -- Mae West pgpKwgPNRt09q.pgp Description: PGP signature
[Puppet Users] Re: [Puppet-dev] ANNOUNCE: 0.25.0beta2 release!
James Turnbull wrote: > This is the beta2 release of Puppet 0.25.0. > > It is available at: > > http://reductivelabs.com/downloads/puppet/puppet-0.25.0beta2.tar.gz > > This is not production ready code - it is a beta release for > testing. There are now packages for Fedora 10/11 and EL 4/5 in my testing repository at: http://tmz.fedorapeople.org/repo/puppet/ If I've botched the packaging or repo setup it's because I'm about to fall asleep. But don't hesitate to let me know about it. And be sure to report any non-packaging bugs to the Puppet bug tracker. :) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Thanks, for a country where nobody is allowed to mind his own business. Thanks, for a nation of finks. -- William S. Burroughs, A Thanksgiving Prayer pgpwBXDGkoRr5.pgp Description: PGP signature
[Puppet Users] Re: Best Practices Rewrite - First Draft
Mark Plaksin wrote: > I'm sure you know this but when you talk about version control be > sure to mention a syntax-checking pre-commit hook. That has saved > us countless hours. This page has hooks for SVN and Git: > http://reductivelabs.com/trac/puppet/wiki/PuppetVersionControl Indeed, this helps a lot for catching the really obvious typos, thanks Mark for helping to work out a good git hook. One potential fix for that is to check for deletions, like so: --- puppet-update-hook~ 2009-07-23 09:53:52.0 -0400 +++ puppet-update-hook 2009-07-23 09:58:11.0 -0400 @@ -15,6 +15,10 @@ do # skip lines showing parent commit test -z "$new_sha1" && continue + +# skip deletions +[ "$new_sha1" = "" ] && continue + # Only test .pp files if [[ $name =~ [.]pp$ ]] then One other potential problem is if puppet is used to manage selinux modules. Compiled modules also have a .pp extension. When adding or updating these files they will pass the "if [[ $name =~ [.]pp$ ]]" check. This can be avoided by not version controlling the compiled modules, but perhaps it might also be reasonable to add a quick bit to the if test, something like this (untested): if [[ $name =~ [.]pp$ ]] && [ "$(file -b "$name" 2>/dev/null)" != 'data' ] The selinux .pp files will return data, while I can't imaging any puppet manifests being labeled as data. :) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ A lot of people I know believe in positive thinking, and so do I. I believe everything positively stinks. -- Lew Col pgpJekzt1x9JV.pgp Description: PGP signature
[Puppet Users] Re: Best Practices Rewrite - First Draft
Mark Plaksin wrote:
>> One potential fix for that is to check for deletions, like so:
>
> Thanks for doing work for us :) We noticed the need for this but
> haven't had a chance to fix it. Your change works great. I updated the
> Wiki.
Cool. Credit for that one goes to Ricky Zhou. When we added this the
Fedora Infrastructure puppet repo, he was the first one lucky enough
to get bitten by it. :)
>> One other potential problem is if puppet is used to manage selinux
>> modules. Compiled modules also have a .pp extension. When adding or
>> updating these files they will pass the "if [[ $name =~ [.]pp$ ]]"
>> check. This can be avoided by not version controlling the compiled
>> modules, but perhaps it might also be reasonable to add a quick bit to
>> the if test, something like this (untested):
>>
>> if [[ $name =~ [.]pp$ ]] && [ "$(file -b "$name" 2>/dev/null)" != 'data'
>> ]
>>
>> The selinux .pp files will return data, while I can't imaging any
>> puppet manifests being labeled as data. :)
>
> This sounds good to me but maybe it's not safe to assume GNU file (which
> supports the -b) is installed on your puppetmaster?
It might not be a safe assumption. Having any file command might not
be safe to assume, really. Worse, the test above wouldn't work
because $name would not be available as a file so the command would
fail. Here's something a little more likely to work (I did test this
one):
diff --git a/puppet-update-hook b/puppet-update-hook
index 539f969..74acaa7 100644
--- a/puppet-update-hook
+++ b/puppet-update-hook
@@ -40,6 +40,9 @@ do
if [[ $name =~ [.]pp$ ]]
then
git cat-file blob $new_sha1 > $tmp
+# SELinux modules also have a .pp extension, try to skip them
+ftype="$((file "$tmp" | awk -F': ' '{print $2}') 2>/dev/null)"
+[ "$ftype" = "data" ] && continue
set -o pipefail
$syntax_check $tmp 2>&1 | sed
's|/tmp/git.update...:\([0-9]*\)$|JOJOMOJO:\1|'> $log
if [[ $? != 0 ]]
If file isn't available, the hook might still try to syntax check a
non-puppet .pp file, but that's no worse than things are currently.
In testing, there are a few other things I noticed. When making an
initial push with this hook enabled, $2 is 00, which causes git
diff-tree to yield an error. Fixing this would require a bit of
fiddling. I'm also wondering if there's any good reason to keep the
'echo diff-tree:; cat $tree' code? It looks like leftover debugging
to me.
One other potential improvement I have is to use shorter commit id's
when telling a user how to check the diff when a problem is found:
diff --git a/puppet-update-hook b/puppet-update-hook
index 74acaa7..38551ef 100644
--- a/puppet-update-hook
+++ b/puppet-update-hook
@@ -49,7 +49,7 @@ do
then
echo
echo -e "$(cat $log | sed 's|JOJOMOJO|'\\${RED}${name}\\${NOBOLD}'|')"
>&2
- echo -e "For more details run this: ${CYAN} git diff $old_sha1 $new_sha1
${NOBOLD}" >&2
+ echo -e "For more details run this: ${CYAN} git diff ${old_sha1:0:7}
${new_sha1:0:7} ${NOBOLD}" >&2
echo
exit_status=1
fi
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
It is impossible to enjoy idling thoroughly unless one has plenty of
work to do.
-- Jerome K. Jerome
pgpa8s86EZckh.pgp
Description: PGP signature
[Puppet Users] Re: ANNOUNCE: 0.25.0 Release Candidate 1 is out!
James Turnbull wrote: > This is the rc1 release of Puppet 0.25.0. There are now packages for Fedora 10/11/rawhide and EL 4/5 in my testing repository at: http://tmz.fedorapeople.org/repo/puppet/ Please report any packaging or repository bugs to me and not to the Puppet or Fedora bug trackers. And be sure to report any non-packaging bugs to the Puppet bug tracker. :) (One repository bug I've noticed is that EL4 does not seem to like the rpm signing key I've been using. I don't know if I just didn't notice this before or if somehow I've managed to butcher the format of the key file. I am pretty sure it's the former, as the changelog for rpm-4.4.2 says "permit gpg to be used for RSA signatures.") -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ A common mistake people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. -- Douglas Adams pgpaWYyRWPdvL.pgp Description: PGP signature
[Puppet Users] Re: Alerts in puppet and puppetmaster
James Turnbull wrote: > It appears you are on leave! Congratulations! As you would know we > all love a holiday. In future though could you consider tuning your > out-of-office email to only respond to mailing lists once. Even once is too much for an autoresponse to a mailing list! But it's often too much to ask that autoresponders be properly configured. :) -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Everyone needs to believe in something. I believe I'll have another beer. pgpx7ZOAIHUKv.pgp Description: PGP signature
[Puppet Users] [PATCH/puppet] ext/nagios: Fix typo in check_puppet.rb script
From: Lance Dillon --- lance dillon wrote: > I tried to post this to puppet-dev but it doesn't look like I have > permission, so here it is on puppet-users for anybody to do something with. > There seems to be a typo in the following file: > > [riffr...@hobbes puppet-0.25.0]$ diff -u ext/nagios/check_puppet.rb.orig > ext/nagios/check_puppet.rb > --- ext/nagios/check_puppet.rb.orig 2009-09-06 20:12:28.0 -0400 > +++ ext/nagios/check_puppet.rb 2009-09-06 20:12:35.0 -0400 > @@ -102,7 +102,7 @@ > exitcode = 2 > when 3 > status = "UNKNOWN" > -exitcide = 3 > +exitcode = 3 > end > > puts "PUPPET " + status + ": " + process + ", " + state > > -lsd Here's a git formatted patch, copied to puppet-dev. ext/nagios/check_puppet.rb |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/ext/nagios/check_puppet.rb b/ext/nagios/check_puppet.rb index 00d9ac9..5013bc5 100755 --- a/ext/nagios/check_puppet.rb +++ b/ext/nagios/check_puppet.rb @@ -102,7 +102,7 @@ class CheckPuppet exitcode = 2 when 3 status = "UNKNOWN" -exitcide = 3 +exitcode = 3 end puts "PUPPET " + status + ": " + process + ", " + state -- 1.6.4.2 -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Never attribute to malice that which can be adequately explained by stupidity. -- Hanlon's Razor --~--~-~--~~~---~--~~ 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 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 -~--~~~~--~~--~--~---
