Jira (PUP-3503) yum provider calls rpm for each managed package

[Charlie Sharpsteen (JIRA)]

Title: Message Title

Charlie Sharpsteen commented on an issue   Re: yum provider calls rpm for each managed package I took a stab at re-producing this on CentOS 6 using a simple manifest: package{'sudo': ensure => present, provider => rpm, }   package{'zlib': ensure => present, provider => rpm, } However, using puppet apply, I only see rpm -q executed during prefetch: # puppet apply pkg_tst.pp --debug --evaltrace   Debug: Runtime environment: run_mode=user, ruby_version=1.8.7, puppet_version=3.7.1   ...   Info: Applying configuration version '1414003271' Info: /Schedule[daily]: Starting to evaluate the resource Info: /Schedule[daily]: Evaluated in 0.00 seconds Info: /Schedule[monthly]: Starting to evaluate the resource Info: /Schedule[monthly]: Evaluated in 0.00 seconds Info: /Schedule[hourly]: Starting to evaluate the resource Info: /Schedule[hourly]: Evaluated in 0.00 seconds Info: Stage[main]: Starting to evaluate the resource Info: Stage[main]: Evaluated in 0.00 seconds Info: Class[Main]: Starting to evaluate the resource Info: Class[Main]: Evaluated in 0.00 seconds Debug: Prefetching rpm resources for package Debug: Executing '/bin/rpm --version' Debug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'' Info: /Stage[main]/Main/Package[zlib]: Starting to evaluate the resource Info: /Stage[main]/Main/Package[zlib]: Evaluated in 0.00 seconds Info: Class[Settings]: Starting to evaluate the resource Info: Class[Settings]: Evaluated in 0.00 seconds Info: Class[Settings]: Starting to evaluate the resource Info: Class[Settings]: Evaluated in 0.00 seconds Info: /Schedule[never]: Starting to evaluate the resource Info: /Schedule[never]: Evaluated in 0.00 seconds Info: /Stage[main]/Main/Package[sudo]: Starting to evaluate the resource Info: /Stage[main]/Main/Package[sudo]: Evaluated in 0.00 seconds Info: /Filebucket[puppet]: Starting to evaluate the resource Info: /Filebucket[puppet]: Evaluated in 0.00 seconds Info: /Schedule[weekly]: Starting to evaluate the resource Info: /Schedule[weekly]: Evaluated in 0.00 seconds Info: /Schedule[puppet]: Starting to evaluate the resource Info: /Schedule[puppet]: Evaluated in 0.00 seconds Info: Class[Main]: Starting to evaluate the resource Info: Class[Main]: Evaluated in 0.00 seconds Info: Stage[main]: Starting to evaluate the resource Info: Stage[main]: Evaluated in 0.00 seconds Debug: Finishing transaction 70134938248580 Debug: Storing state Debug: Stored state in 0.05 seconds Notice: Finished catalog run in 0.27 seconds I also added a debug statement to puppet/provider/package/rpm.rb:87 to ensure calls were traced, but it was not tripped. David Schmitt: Could you provide more information about the conditions this is occurring under? An example manifest that triggers the problem would be awesome. Add Comment   Puppet / PUP-3503 yum provider calls rpm for each managed package When managing packages with package/yum, the provider calls rpm for each package, even if nothing has changed and the provider's cache should be hot. With a handful of packages this is not really a problem, but at a client's site we have added 1200 packages, which translates into approx. three minutes runtime just for checking the current state. I'v... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.