similar to: Resource dependencies

Hello, I just attempted to remove both the ypbind and the yp-tools packages using the package parameter with yum. As it turns out, both of these packages depend on each other. Is there a way of forcing package removal and, if there is not, is there a way of making all packages to be removed be collapsed into the same yum command? Either of these solutions would solve the problem with the

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,

There was a discussion a while ago about adding inheritance to definitions. There is a need for a way to specialize parameters while allowing passing other options. This comes up with remotefile where it would be nice to have a default server location but not specify all the parameters (and their defaults) in the definition. Was there a change to the syntax? Is there a way to accomplish this?

Hi, in an attempt to simplify my configuration, and from a suggestion on IRC, I was thinking of using multiple values for file { source => [] }. Was just currious if anyone had any comments on this. Basically, I setup my file-server to use: <snip> [private] path /var/lib/puppet/files/private/%H allow * [shared] path /var/lib/puppet/files/shared allow *

My head hurts from trying to figure this out for the past several hours . . . I want to determine what provider to use based on a fact (thanks for the suse version fact btw) but I ain''t gettin it: What''s wrong? Am I going down the completely wrong path? Is there a better way? # suse-yum.pp case $suse_repo_name { #sled10-i586: {Package{ provider => rug}} sled10-i586:

I''m trying to scale up Puppet and am wondering if I can use Puppet in an odd way. I''m looking to use Puppet as an authoritative source for all the configuration done to a cluster. That includes fstab''s, modprobe.conf, etc. This reduces duplication. I''m using SystemImager on a cluster and would like to run Puppet during the install, so when the node reboots, it

How are people upgrading puppet itself on their hosts that run puppetd? Can puppet be used to upgrade to a new puppet package via gem, rpm or some other package provider? How do you handle restarting? Just hoping theres a better way than "ssh and a for loop" or having to have another configuration management system installed.

I am trying to set a "subscribe" for a Yumrepo object so that an Exec "yum clean all" is ran immediately after a Yumrepo is changed. With the following setup, I am not seeing the "subscribe" fire off until after Packages that have a require pointing to the Yumrepo["custom"] are attempted to be installed. Is in right to expect that the subscribe on the

Hi folks, I''m trying to get my feet wet in puppet-land. I''ve successfully installed a puppetmaster and client and managed to get them to do something (the sudo file-permission example as explained in the tutorials). Now I''m trying to do something a bit more complex using defines but nothing seems to happen anymore. Config files involved: ###### site.pp filebucket {

Just started a "pilot" puppet server for real after messing around in VMs for the past week or so... I used the 0.24.0 since it was available, and on the test run, got this: err: Could not prefetch package provider ''yum'': Execution of ''/usr/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py'' returned 512: /usr/bin/python:

Hi, I''ve writen a draft describing puppet on SuSE/opensuse linux. http://www.reductivelabs.com/trac/puppet/wiki/PuppetSuSE Any feedback is welcome. Martin

I am just starting with puppet to replace a ''homegrown'' config distribution system and it is looking very promising, i will be playing with the templating next. I have run into an error when attempting to disable the shipped repo''s with CentOS 4.4. See the relevant info below. This is obviously a problem when repo definitions include multi-line baseurl''s.

Greetings all, (Hopefully this won''t be a HTML mail.) I''ve picked up puppet as a tool to manage a fairly small network of RHEL servers, and I''m really liking what I see so far. However, I''m having a pile of trouble with a class definition for a yum controller: # $Id$ class yum-rhel5 { file { "/etc/yum.conf": mode => 644,

Hello. I''m a long time cfengine user, some might say sufferer, and I have finally managed to get around to experimenting with Puppet. So far I''m very impressed. I am trying to get puppet to configure the openntpd config file, from an ERB template, based on the node definition in the site config. What I''m trying to understand is why when I define a variable in a child

I am trying to write a definition that downloads and extracts a tar file if the destination directory does not exist. The tar file won''t change and does not need to be download and extracted if it changes. The definition I am using now is: define remote_tar($source, $directory) { remotefile { "/tmp/$name.tgz": source => $source, } exec {

Ok, given the statement on the web page about unlesssystemuser under Resources ( http://reductivelabs.com/projects/puppet/documentation/typedocs.html#resources), I assume that users can be purged. However, when I attempt to do this with resources { user: purge => true, noop => true } and what I get is: err: Found a bug: private method ''split'' called for nil:NilClass.

I''m trying to use Puppet 0.19.3 to manage Yum repositories, using the ''yumrepo'' type. Our repository configuration files currently have a line baseurl=file:///net/yum/CentOS4.1/$basearch/ where "$basearch" gets interpreted by ''yum''. I''ve tried the line baseurl => "file:///net/yum/CentOS4.1/$basearch/" in my

I think I''ve got every fix except one in that''s going to make it into grover, which I''ll hopefully be releasing tomorrow. I plan on adding Tim Stoop''s patches for home directory management (#432), but everything else is getting pushed to the next release at this point. I''ve fixed all of the major bugs, or at least I think I have. If

Hello, I have two Vmware images, with 256MB of RAM memory each one, running puppetmasterd for the server and puppetd for the client. It''s normal that my puppetmasterd and puppetd occupies almost 10% of RAM memory each one? They aren''t doing anything especial, just listening on the ports. Thanks.

Puppet version: 0.22.4 facterversion => 1.3.7 rubyversion => 1.8.5 Given the following: file { yum_repo_d: path => "/etc/yum.repos.d", ensure => directory, recurse => true, purge => true } yumrepo { pkg_repo: descr => "Packages Repository", enabled => 1, baseurl => "http://Some/path/", gpgcheck => 0,