similar to: yumrepo is missing name attribute in repo files using puppet-0.24.8-4.el5

Hello All, In all the examples that I see you configure one repo per file; i.e: yumrepo { "testing.com-repo": baseurl => "http://repos.testing.com/fedora/$lsbdistrelease/", descr => "Testing.com''s YUM repository", enabled => 1, gpgcheck => 0, } But how do I specify multiple entries to the same file?. For instance, I just one to have one

Just upgraded to 2.7.6 and the yumrepo type does not write out our yum configs correctly, anyone experiencing this? Documentation hasn''t changed from what I can tell for this type. # facter -version 1.6.2 # puppetd --version 2.7.6 # facter architecture x86_64 # facter operatingsystem Fedora # facter operatingsystemrelease 14 ==== My manifest ==== yumrepo {

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.24.8 is now available! This is a maintenance release for the 0.24.x branch but contains a small number of new features including some significant performance enhancements for large installations and stored configurations. The tarball is available at: http://reductivelabs.com/downloads/puppet/puppet-0.24.8.tgz MD5 hash:

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:

hello list.. I am sharing a yum configuration in a class (centos.pp) between two nodes. But the yum configuration doesn''t apply at all to one node even tho it does to another identically configured node. ## packages are failing to install via yum on one ec2 aws instance and another identical ec2 instance works fine [root@kromep2 ~]# cat /etc/redhat-release CentOS release 5.5 (Final)

Hello All, How do I specify a variable that has a space in it? I''m trying to setup a yum repo that has two different baseurl''s based on the product name ($productname). Default goes one way, but if the product is "PowerEdge 2650" then is a different URL. The thing is, that is only picking up the default. How should I specify the value with the space in the

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,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1 release is a maintenance release in the 0.25.x branch. The release is available at: http://reductivelabs.com/downloads/puppet/puppet-0.25.1.tar.gz http://reductivelabs.com/downloads/gems/puppet-0.25.1.gem Please report issues and feedback via the Reductive Labs Redmine site:

I was working with yumrepo, defining new entried and seeing them appear in /etc/yum.repos.d After considerable tinkering, and with the sad discovery that resource { ''yumrepo'': purge => true } does not work, I moved my working /etc/yum.repos.d to /etc/yum.repos.d-old and re-ran my catalog. To my surprise, the repo entried were appended to /etc/yum.conf Long story short: I

I have installed puppet from puppet-labs yum repository on OEL familiy of Red Hat Enterprise Linux Server release 5.9 (Tikanga) ---------------------------------------------------------------------------- [root@oel-puppet-master modules]# yum list facter Loaded plugins: rhnplugin, security This system is not registered with ULN. You can use up2date --register to register. ULN support will be

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

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

Hi, 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/ But when i run the client side daemon i get this message: info: /Class[main]/Node[basenode]/Class[inittab]/File[inittab]/source: No specified sources exist err:

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,

Hi, When you set managehome to false on a User ressource, homedir will still be created on a CentOS box as the -M flag is not passed to useradd. $ diff -u /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/ useradd.rb.bak \ /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/useradd.rb --- /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/ useradd.rb.bak 2008-10-23 01:19:07.000000000 +0200

Hi all, I am creating a recipe for rhel boxes which needs to determine what type of install is present (server or client). I thought I would use the facter fact lsbdistid for this purpose but when I run "facter lsbdistid" from the command line nothing is returned. If I just run facter and grep for lsbdistid, what I am looking for is returned. Does anyone know why this might be?

Hello Puppet list, I am taking over the puppet configuration of a sysadmin who left, and am having troubles deploying puppet to a new node. We are using puppet v2.7.3 both on the client and the puppetmaster, on Ubuntu 10.10. The node asks for a certificate fine, and I signed it on the puppetmaster. For the following logs extract I ve replaced the FQDN of my node by puppet.example.com. When doing

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. Douglas. -- You received this message because you are subscribed to the

Hey Folks, I''m looking at doing automated provisioning of new servers and am trying to integrate puppet into this process. What I''m wondering though is what the best process for securely registering a new node is. At the moment the first time puppet is run I have to then accept the certificate on the puppetmaster and then run puppet again. What I would like to do is accept the