On Tuesday, August 14, 2012 9:07:39 AM UTC-5, trey85stang wrote:
>
> Well no go with metadata_expire or a yum clean all after updating the
> repo. This appears to be a bug of some sort. Debugging output shows
> before any packages checked this output:
>
> debug: Prefetching yum resources for package
> debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm --version'
> debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -qa
> --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION}
> %{RELEASE}
> %{ARCH}
>
>
> ''
>
>
> debug: Puppet::Type::Package::ProviderYum: Executing '/usr/bin/python
> /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py'
>
> I am thinking puppet somehow uses this information throughout the puppet
> run, to verify packages are the latest. The obvious problem is this
> doesnt get updated if a repo is updated. Hopefully I can get this worded
> correctly and into a bug report.
That's determining what packages are already installed. Yes, the
information will be used throughout the run, but it does not depend on the
configured repos (in fact, note that it's not even running 'yum' itself,
but rather 'rpm'). None of that is buggy.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/VR3b58RDSdMJ.
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.
