Puppet users - May 2007 - YUM provider bombs out on ''latest'' if the server is not available.

I''ve noticed that, should the yum server go down, any packages
requiring the ''latest'' version get thrown an error and
anything
depending on them does not run.

This does not seem to be correct to me since, should a yum provider
not be available, the installed version (if one is installed) should
be considered the latest version.

I hacked a ''rescue'' line into the yum.rb provider under
''def latest''
that simply changed the ''output'' variable to an error message,
and
that seemed to fix the problem.

I''m not sure if this is the best way to do things given the
''catch
all'' nature of the solution, but it seems to work....

Thanks,

Trevor

On May 16, 2007, at 2:02 PM, Trevor Vaughan wrote:
> I''ve noticed that, should the yum server go down, any packages
> requiring the ''latest'' version get thrown an error and
anything
> depending on them does not run.
>
> This does not seem to be correct to me since, should a yum provider
> not be available, the installed version (if one is installed) should
> be considered the latest version.
>
> I hacked a ''rescue'' line into the yum.rb provider under
''def latest''
> that simply changed the ''output'' variable to an error
message, and
> that seemed to fix the problem.
>
> I''m not sure if this is the best way to do things given the
''catch
> all'' nature of the solution, but it seems to work....
David Lutterkort wrote the yum provider, so I can''t speak  
specifically of what the best option is, but if it works for you...

Can you file a bug with a patch?

  --
  I take my children everywhere, but they always find their way back  
home.
              --Robert Orben
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com