On Oct 25, 10:04 am, Brad <bradw...@gmail.com> wrote:
> 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 retrieve current
> state of resource: A section with name updates already exists
[...]
> notice: //yumrepos::fixperms/File[/etc/yum.repos.d]: Dependency
> yumrepo[centosplus] has 1 failures
[...]
> warning: //yumrepos::fixperms/File[/etc/yum.repos.d]: Skipping because
> of failed dependencies
>
> I took a look at /etc/puppet/modules/yumrepos/manifests/init.pp, and
> it looks normal.  I'm wondering if there's a conflict somewhere in
> another file, but I'm not sure which file that would be; nodes.pp
> looks normal, and this node isn't controlled by anything within /etc/
> puppet/services.  I am not receiving messages like this on any other
> node, and have not received this message on this or any other node in
> the past.
>
> Any ideas would be very much appreciated.  Thanks!

Check the yum configuration on the affected client: I suspect you will
find a duplicate definition of repository "updates".

grep updates /etc/yum.repos.d/*


Cheers,

John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to