On 08/18/2011 06:56 PM, Jakov Sosic wrote:
I encountered a following problem, if I state for example:
package{"aspell-en": ensure => absent, }
package{"aspell": ensure => absent, }
I get error in logs because of dependencies. It seems that puppet uses
'yum' for installation on CentOS and 'rpm -e' for removal of packages,
so it cannot handle this kind of dependencies:
# rpm -e --test aspell-en
error: Failed dependencies:
aspell-en is needed by (installed) aspell-0.60.3-7.1.x86_64
# rpm -e --test aspell
error: Failed dependencies:
aspell>= 12:0.60 is needed by (installed) aspell-en-6.0-2.1.x86_64
This is a long-standing bug, and one that I consider fairly major but
has been hard to get puppetlabs focused on.
- The circular deps bug was reported 2 years ago.
http://projects.puppetlabs.com/issues/1935
- A few months later a patch is submitted to batch rpm transactions.
This solves the circular-deps issue and also has significant
performance benefits during puppet runs with many package installs.
http://projects.puppetlabs.com/issues/2198
This comes up periodically and inevitably someone proposes that the
architecturally "correct" solution is for RedHat not to employ circular
deps, which shuts down discussion of a potential solution for another
3-6 months:
http://groups.google.com/group/puppet-users/browse_thread/thread/8a083899386909d5/
http://groups.google.com/group/puppet-users/browse_thread/thread/9cbeadad62741b0a/
Denmat wrote:
and see if you can order it. You might also get luck from 'before => '
Ordering doesn't matter, the dependencies involved are rpm-deps, not
puppet-deps. In order to succeed, the action has to be atomically
performed in a single rpm call (which requires #2198 to land and enable
batch transactions), or it has to be performed with a
rpm-dependency-aware tool like yum (but that has it's own problems
discussed below).
Jonathan Gazeley wrote:
Is it possible to force use of the yum backend for package
removals like this?
package { ['aspell', 'aspell-en']:
ensure => absent,
provider => 'yum',
}
Jakov Sosic wrote:
No, it uses rpm and that's it. And it cycles through the list item
by item. If it would only run rpm -e package1 package2, but not
even that
devzero2000 wrote:
The right answer is
ensure => purged as this tell puppet to use yum -y (and not rpm) in
the yum provider.
As devzero notes, ensuring "purged" will force the yum-provider to use
the yum-command instead of the rpm-command for package removals, but
that's a good way to get a box blacklisted by Redhat for pinging their
update-servers too often. Yum will be run for every single package that
you manage this way, and will update its package catalog every time,
resulting in what looks like misconfiguration or dos to RedHat.
In my opinion, this bug makes the yum provider very close to useless.
I'm watching bug #2198 closely to see if it ever lands, but it seems to
be very low on the priority list given that there's been a patch sitting
unmerged for almost two years.
Folks who work around this issue do so with execs, but I think more
often people just give up and let unneeded packages build up like cruft.
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.
