similar to: Using multiple values for source, for platform/arch/host configs

Has the component/type defaults syntax changed for 0.22.x? I have a component: <snip> define remotefile($owner=root, $group=root, $mode, $source, $backup=false, $recurse=false, $groupname="default") { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

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,

One one of my new vmware guests... puppetd -v spits out a bunch of err & warnings about "State group failed"... what does this mean? <snip> info: Caching configuration at /var/lib/puppet/localconfig.yaml err: Could not create root: Could not find a default provider for group warning: file=/etc/yum.repos.d/: State group failed: Could not find a default provider for group

Hi, I''m running into a problem with the user type with puppet 0.20.1... this worked before with 0.19.x at least, not sure about 0.20. But I''ve got adduser.pp: <snip> define adduser($uid, $gid, $groups="users", $membership="minimum") { group { $name: gid => $gid, allowdupe => false, ensure

Why doesn''t the yum provider support version, I tried added ensure -> ''ver'' and it barfs up (on clients) with: <snip> err: //stan.gbuild.org/any-host/java/Package[j2sdk]/ensure: change from 1.4.2_12-fcs to 1.4.2_13-fcs failed: Package provider yum does not support specifying versions at /etc/puppet/manifests/classes/ java.pp:13 </snip>

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

So, looks like the latest facter has fqdn... cool. but for some reason templates can''t access it. I was defining $fqdn in my site.pp, but had to remove it after the last yum update, which brought in a new facter package. But now my templates can use fqdn. Why would this happen? --jason

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

For example, I have a bunch of package resources defined for packages which are contained in the yum repositories defined by the yumrepo resources. If the package is installed first, then it will fail because the repository is not available. I know about "require". But I would prefer not to add a direct dependency on the source repository. Is there an easier way to do this? What

I have a few different groupings of hosts, and I am wondering what is the best way to organize the node configuration for them. I have a few machines that are VMware hosts, a bunch of VMware guests, and the main admin server which runs a bunch of stuff like puppetmasterd. I''ve got a bunch of classes/*.pp which define configuration for sudo, yum, java, etc. Right now I just have

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:

Maybe it works, maybe it doesn''t, but I sure as hell can''t make it work. I get stuck with "Could not find object(s)" whatever I do This is my module init.pp class ztest::setup { notice "MAIN SETUP CLASS" file { directfile: path => "/etc/directfile", owner => root, group => root, mode => 0644, content

Hello - Is the following a configuration issue (which is usually the case) or a bug? I''m trying to ensure a local user is present in a NIS environment using the following recipie: class dduck_add { user { "dduckl": ensure => present, uid => 60030, gid => "100", groups =>

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

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

Hi, I just got my local yum repo setup so that I can use puppet to install packages... and it looks like something is not working. <snip> Tue Sep 19 02:13:05 PDT 2006 Puppet (notice): Starting configuration run Tue Sep 19 02:13:10 PDT 2006 //default/java/package=jdk/ensure (err): change from absent to latest failed: Could not update: Could not execute ''/usr/bin/yum -y install

Hi Folks, Just wondering what the above error means. I followed the instructions in http://www.howtoforge.com/installing_puppet_on_ubuntu and when I try to startup the server it fails with the error in the subject of this message. I am running the server on Ubuntu/i386/gutsy. In particular, # puppetmasterd --verbose --debug debug: puppetmasterd: Setting logdir to

Hello, i use a file type to manage sysctl.conf. For some work i override this file by doign File[''/etc/sysctl.conf''] and i have an exec refresh only to run sysctl -p so it reread the sysctl.conf file if changed. My issue is that at each run i got, i start in state when i see the overriden one on the server: 1st run, i have the basic sysctl.conf not the ovveriden one

I forgot to mention this in my announcement yesterday. Puppet facts are no longer downcased in the language, and string comparisons now default to being case-insensitive. Where your operating system might previously have been ''solaris'' or ''debian'', it is now ''Solaris'' or ''Debian''. However, you can still do comparisons