robbyt wrote:
> For some reason, I'm unable to manage cron resources on my CentOS5
> server:
>
> manifest:
>
> cron { "test":
> command => '/bin/true',
> user => 'root',
> hour => '1',
> }
>
> And when I try to run this via puppetmasterd:
>
> info: Caching catalog for ny-dev84.domain.com
> err: Could not prefetch package provider 'yum': Execution of '/usr/
> local/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/
> yumhelper.py' returned 1: <type 'exceptions.AttributeError'>
>
> info: Applying configuration version '1264214417'
> notice: //crontab::puppet_runner/Cron[test]/ensure: created
> "-":5: bad command
> errors in crontab file, can't install.
> notice: Finished catalog run in 3.69 seconds
>
>
> There are two things here that confuse me. 1: what's the deal with the
> 'could not prefetch package provider' and 2: why does "/bin/true"
> result in "bad command"?The fact that the error points at /usr/local/bin/python makes me wonder if you've got some non-packaged version of python in your path. The cron error sounds like the problem with 0.25.3, though I can't recall if that's the output that bug causes or not. What version of puppet are you running? If you're using EPEL packages of 0.25.x from epel-testing, then update, as we have pushed 0.25.3 packages with the problematic cron changes reverted. -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I got nasty habits. I take tea at 3.
pgp1tvJTXepLW.pgp
Description: PGP signature
