similar to: Yumrepo''s subscribe ran before package require Yumrepo?

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)

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 {

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:

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,

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

I''m using puppet-0.24.8-4.el5 on CentOS 5.4. My problem is yumrepo isn''t writing the "name=" field to the repository files which causes yum to complain with the error: Repository ''local-CentOS-5.4-x86_64'' is missing name in configuration, using id I get this behavior on all of my yumrepo definitions. One of them looks like this: yumrepo {

Hi all Does anyone know what causes this error? I have setup a local CentOS repository, with mrepo, and can succesfully use it for updates & installation of just about anything. Yet, this error comes up. Here's my /etc/yum.conf: # PUT YOUR REPOS HERE OR IN separate files named file.repo # in /etc/yum.repos.d [base-local] name=CentOS-$releasever - Base #mirrorlist=

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

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,

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

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

Hello, I''m currently running Puppet 0.25.5-1 on CentOS 5.5. Everything has been going swimmingly until a couple of weeks ago, when I began receiving errors on one of my nodes. The node in question is also my puppetmaster, but the errors seem client-related. The errors are: err: //yumrepos::centosbase/Yumrepo[addons]: Failed to retrieve current state of resource: A section with name

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.

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

Hello puppet masters, I am cleaning up some puppet modules, using puppet-lint. The warning I am getting is: top-scope variable being used without an explicit namespace I can turn this particular check off, but in doing my research I''m finding all sorts of messages saying to avoid using +=, to avoid using variables in the node scope, and to switch to a parameterized class whenever

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 {

what is the best way to handle package conflicts between classes? for example, below, i have the following two classes defined and both include a "package { "perl-LDAP" }", so when used separately they work as expected but when i need to assign both classes to a node i get a conflict. error: "Duplicate definition: Package[perl-LDAP] is already defined" thanks

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

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 trying to get a package (iftop) installed on a test node using puppet but I can''t get it to install. This seems like it should be simple, but I can''t figure out what I am missing. Have done a lot of searching for similar problems and the answers I found seem to be vague in the details and explanation. I have the package added to an internal yum repo. OS is Centos 5.4.