similar to: package provider multiple defaults

I tried to open a Trac ticket on this, but the menus are not working for some reason right now. I''ve noticed this in our puppetmasterd logs since upgrading: puppetmasterd[7943]: Could not call: nested *?+ in regexp: /^\/var\/www\/html\/download\/NSClient++-0.2.7.zip/ Seems like the data passed should have RE characters quoted (ala \Q...\E in Perl) prior to this test. Regards, Mark

I thought this made sense, but apparently I am mistaken: define copyfile($owner = root, $group = root, $repo = "config", $mode, $source = $name, $purge = false, $backup = false, $recurse = false, $server = $servername) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

I''ve tried replying twice in the past few days to a request for more information on a bug I filed. When I do, I get: ----- The following addresses had permanent fatal errors ----- <trac@reductivelabs.com> (reason: 550 5.1.1 <trac@reductivelabs.com>: Recipient address rejected: User unknown in local recipient table) Regards, Mark -- Mark D. Nagel, CCIE #3177

I have a client I''m testing where the puppetd process grows slowly (over a few days) to the point where it exceeds 100MB. This triggers an alert and we restart the daemon, but I''m curious whether anyone has noticed similar behavior. Details are: Server: CentOS 4.5 x86 (on VMWare Server guest) RPM install from dlutter repo (puppet-0.23.2-1.el4) The only thing I can

I have found a few issues with puppet and the up2date provider (version 0.22.4) that I''d like to run by those who use up2date (to see if others are experiencing the same issues). 1. Puppet doesn''t seem to find the latest updates of packages that are already installed. In looking at "/usr/lib/site_ruby/1.8/puppet/provider/package/up2date.rb", I found that

Hello there, Since the update with ruby all my puppet function is dead (well known issue with the cert) . There has been some discutions on the dev list on how to patch this for future versions. I have read the list and wondered how we can solve the issue while waiting for the .24. I am in beta test of the .23.x version but on my production system i wanted to find a way to solve this now

Hi, I have this small problem with my servers managed by Puppet (i have a workaround so the problem is not so important): 1) These servers are installed with Red Hat Linux Enterprise and i use Puppet in client-server mode. 2) I''ve made a Puppet class called "yum" to install (by the RPM package provider) and configure YUM on my servers. I don''t use the YUM package

In the normal override method, you can change the value of a parameter, but can you unset a parameter? file { "/etc/somefile": mode => 644, owner => "dude" } File ["/etc/somefile"] { mode => unset } ??

Is it possible to have a file copied from the fileserver but only when it doesn''t exist? I want to prevent changes on the client from being wiped out if it is different. We have a couple of config files that the DBAs are resistant to managing through puppet. They currently manually deploy changes and I don''t want those changes wiped out if the server isn''t updated. I

What is the right way to write definition so that defaults can be overriden? $puppetdir = "puppet://$server/files" define remotefile($source, $owner = "root", $group = "root", $mode = 0644, $backup = false, $recurse = false) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

Hello, I use puppet with RHEL and there are some packages that aren''t in up2date/yum repositories. I need a way to get these specific RPMs installed. There''s a blog posting that describes an almost-perfect way to do it: http://www.raskas.be/blog/2007/09/10/managing-user-passwords-with-puppet-on-centos/ The only problem with his example is that the RPM will always in the /tmp

On the module organization wiki, we''re got the following statement: To control access to the files in modules, the fileserver configuration can contain an explicit declaration of a ``modules`` module:: ... however, I thought the fileserver couldn''t define module or any section that is in the module paths. Has anyone tried this? And if it doesn''t work, is there

Currently, facter returns the kernel version as both the kernel and operatingsystemrelease facts. I would like to change that so that on Fedora, operatingsystemrelease is the release number (5,6,7 etc.) or ''Rawhide'' ... are there any objections to making that change ? David

I just realized that if you don''t have redhat-lsb on your (Fedora 7) box, all those lsb* facts don''t show up. Should I make redhat-lsb a requirement for the facter rpm to guard against that ? David

hi all, we maintain about 30 puppet managed nodes. the version of the clients is 0.23.0 and 0.23.1. the master is 0.23.0. today we installed a new CentOS 5 node with David Lutterkort''s puppet 0.23.2 rpm. this host is a reinstall of an old FC4 on new hardware. we are getting this error on 0.23.2, never happened before: | Could not retrieve configuration: | Failed to parse template

I have a machine with two swap partitions (sda2 and sda8). Both will have none as mount point. When I try to use puppet (using mount type) for managing fstab I get problems because "name" in both instances (i.e. mount path) will be "none". How should I fix this within puppet? Regards Halvard Moe

I updated to 0.22.3-1 from the dlutter repo (CentOS 4.4) and I''m still having trouble adding new nodes as others saw from the previous version, though I believe the error is different now. The procedure I used was: <client> /etc/init.d/puppet once -v <server> /usr/sbin/puppetca --sign nodename <client> /etc/init.d/puppet once -v This used to work for new nodes, now I

Hi all, Not sure if this is a bug in puppet, yum, or just something I''m doing wrong. I''m trying to use puppet to update a package to a particular version and exec a command when that update is applied. The problem is, puppet calls yum which successfully updates the package, but puppet then thinks the update has failed and hence doesn''t trigger the exec. Next

Hello, I just installed the latest version of puppet and puppetmaster on an up to date RHEL4 system. If I turn on ''storeconfigs'' on the puppetmaster server I get the following error: debug: Calling puppetmaster.getconfigerr: Could not retrieve configuration: Uncaught exception No such file to load -- sqlite3 in method puppetmaster.getconfig I have gems and rails installed

This is a new one for me. What does it mean? I don''t recall these configs giving me this problem before: RPMs must specify a package source in file /var/lib/puppet/manifests/modules/ssh.pp at line 18