search for: yumrepos

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

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 updates already exists err: //yumrepos::epel/Yumrepo[epel]: Failed to retrieve current state of resource: A section with name updates already exists err: //yumrepos::centosbase/Yumrepo[base]: Failed to re...

...sled10-i586: {Package{ provider => rug}} sled10-i586: {Package{ provider => yum[sled10-i586] }} sles10: {Package{ provider => yum["sles10-i586"] }} sles9-i586: {Package{ provider => yum["sles9-i586"] }} } $server = "puppet.example.com" class yumrepos-suse { yumrepo { sles9-i586: descr => ''SuSE Linux Enterprise Server 9'', enabled => 1, gpgcheck => 0, baseurl => "http://$server/sles9/" } yumrepo { sles10-i586: descr => ''SuSE Linux Enterprise Server 10'', en...

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 {

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

...nothing seems to happen anymore. Config files involved: ###### site.pp filebucket { # use a filebucket on the puppet server main: server => puppet } import "definitions/*" import "classes/*" import "templates" ###### templates.pp node basenode { include yumrepos } ###### classes/yumrepos.pp class yumrepos { yumrepo { dag: } } ###### definitions/yumrepo.pp define yumrepo () { file { "/etc/yum.repos.d/$name.repo": mode => 644, owner => root, group => root, backup => true, recurese => false, ensure =&...

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 *

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 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

I'm using yum-pull for creating a local yum repo. I have a non-root user that runs the script and the files are stored in that user's home directory. I'm trying to make that directory available with httpd. The user owns all the files and subdirs and the rights on all the files is: -rw-r--r-- I added this to the bottom of httpd.conf and restarted httpd. Alias /repomirror

...ng with: ----------------------------------------------------------------- node ''chromews21.acadaca.net'' inherits webserver { ## <-- instead what I attempt to do is setup the stage relationships here class {"centos": stage => os} class {"yumrepos": stage => repos} class {"baseapps": stage => main} class {"basefiles": stage => main} class {"apache": stage => last} } ------------------------------------------------------------------------------------------- So obviously...

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)

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.

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,

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 used to have something like this: yumrepo { "foobar": [...] gpgkey => ["file:///etc/pki/rpm-gpg/key1", "file:///etc/pki/rpm-gpg/key2"], } Which as expected used to generate files looking like this: [foobar] gpgkey=file:///etc/pki/rpm-gpg/key1 file:///etc/pki/rpm-gpg/key2 It appears this no longer works with 0.24.6. I''m pretty sure it

I have a class that pulls in some yum repositories. One of the yum repositories is disabled, but on one host I''d like to enable it. i.e. I''d like to do something like this: class { ''myyumrepos'': } yumrepo { ''EPEL'': enabled => 1, } What''s the best way to do this? I am using an ENC. -- Biltong biltong@fastmail.fm -- http://www.fastmail.fm - Email service worth paying for. Try it for free -- You received this message because you are subscrib...

Hi, I am trying to create a mock configuration file that points to my local dnf repo. I have the following in the mock config template: [local-repo] name=my-Local baseurl=http://yumrepo.example.com/yum-repository/local/centos/8/x86_64/ failovermethod=priority skip_if_unavailable=False When I try to run mock I get the following error: (vgeppetto3 pts18) $ mock -v -r epel-8-x86_64