On 01/17/2011 12:40 PM, Matt wrote:
Unfortunately thats a limitation of RPM which has been worked around
with YUM. YUM will do the resolution of dependencies if they are also
in one of the repositories configured on the system.
Unfortunately RedHat will blacklist systems that run yum too often so
you either must:
1) Not manage packages with circular dependencies using puppet. This is
what I've opted to do, although I find it unfortunate since puppet would
be my preferred venue to do this kind of thing otherwise.
2) Use the yum-driven options *AND* run your own satellite server so you
can ping it as often as you like. This is possible but is a not
insignificant amount of unnecessary work.
3) Use the yum-driven options and reduce the frequency of puppet-runs to
a few times per day in order to stay below the RedHat's abuse threshold.
4) Use rpm -i exec's instead of the package provider.
While these workarounds are all feasible, none of them are nearly as
desirable as batched transactions that properly support circular
dependencies. I know Luke has also expressed his opinion that this is
an upstream problem that affects an insignificant number of users
(http://projects.puppetlabs.com/issues/1935), but I would *really* like
to see this patch land. Between bugs 1935, 4893, 3156, 2198, and this
thread, it looks like at least 8 people have reported this affecting
them over the last two years. The batchable transactions fix is
straightforward, improves performance of puppet-runs, and has no
downside that has been discussed in its bug.
Cheers,
Mike Lococo
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@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.
