It looks to me like yum itself is broken.  Try installing something using the 
yum command-line client.

On Apr 12, 2010, at 7:24 PM, dbs wrote:

> Okay, I'm stymied.  I set up a rule to kick a new .repo file out to
> my
> clients into /etc/yum.repos.d/ called 'lwm.repo'.
> 
> The rule says:
> class lwm-repos{
> 
>       file { "/etc/yum.repos.d/lwm.repo" :
>               owner => "root",
>               group => "root",
>               mode => 444,
>               source => "puppet:///lwm-repos/lwm.repo",
>               notify => Exec["updatecache"]
>       }
> 
>       exec { "updatecache" :
>               path => "/usr/bin:/usr/sbin:/bin",
>               command => "yum makecache",
>       }
> }
> 
> The .repo file was disted out, but I started getting:
> 
> Apr 12 21:29:23 bos-rep-etl01 puppetd[5135]: Caught TERM; calling stop
> Apr 12 21:29:23 bos-rep-etl01 puppetd[5486]: Reopening log files
> Apr 12 21:29:23 bos-rep-etl01 puppetd[5486]: Starting Puppet client
> version 0.25.4
> Apr 12 21:29:24 bos-rep-etl01 puppetd[5486]: Could not prefetch
> package
> provider 'yum': Execution of '/usr/bin/python
> /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py'
> returned 1: Traceback (most recent call last):   File
> "/usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py",
> line
> 115, in ?     ypl = pkg_lists(my)   File
> "/usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py",
> line
> 40, in pkg_lists     my.doTsSetup()   File
> "/usr/lib/python2.4/site-packages/yum/depsolve.py", line 72, in
> doTsSetup     return self._getTs()   File
> "/usr/lib/python2.4/site-packages/yum/depsolve.py", line 85, in
> _getTs
>    self._getTsInfo()   File
> "/usr/lib/python2.4/site-packages/yum/depsolve.py", line 91, in
> _getTsInfo     self._tsInfo.setDatabases(self.rpmdb, self.pkgSack)
> File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 537, in
> <lambda>     pkgSack = property(fget=lambda self: self._getSacks(),
> File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 392, in
> _getSacks     s
> Apr 12 21:29:24 bos-rep-etl01 puppetd[5486]:
> (//lwm-repos/Exec[updatecache]/returns) change from notrun to 0
> failed:
> yum makecache returned 1 instead of one of [0] at
> /etc/puppet/modules/lwm-repos/manifests/init.pp:17
> Apr 12 21:29:24 bos-rep-etl01 puppetd[5486]: Finished catalog run in
> 0.54 seconds
> 
> Now I cannot make those messages DISAPPEAR.  I've disabled the Notify,
> disabled the exec block in the rule, heck even commented out the
> 'include' in the nodes.pp that includes that module.  I added
> ignorecache to the client puppetd.conf file, but no dice there either.
> 
> Questions : is this the proper way to get a .repo out onto the client
> machine?
> 
> And... what's causing this error message?
> 
> Server: CentOS 5.4 puppetmaster 0.25.4
> Client: CentOS 5.2 puppetd 0.25.4
> 
> Help please!
> 
>    -d
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
> 

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

Reply via email to