I haven't played with this aspect of Cfengine yet, but I do know that Cfengine caches yum output to reduce its resource footprint. Could it be Cfengine cached v24 and then v26 became available at the repo but Cfengine is still looking at its cache where it sees v24 as the latest version? Just a wild guess. You could test it by changing the value for how long to cache yum output, its configurable, look under the hood of yum_rpm.
Aleksey On Mon, Jul 18, 2011 at 12:54 AM, <no-re...@cfengine.com> wrote: > Forum: CFEngine Help > Subject: Re: yum_rpm automatic package upgrades > Author: svenXY > Link to topic: https://cfengine.com/forum/read.php?3,22812,22820#msg-22820 > > nobody? > Is this so uncommon? > > Furthermore, this fails also: > > > vars: > "old_java_rpm" string => "1.6.0_24-fcs"; > > some_class:: > "jdk" > handle => "add_package_jdk", > comments => "install RPM package", > package_policy => "addupdate", > package_version => "${old_java_rpm}", > package_select => ">", # note: greater than > version!!! > package_architectures => { "x86_64", }, > package_method => yum_rpm; > > > I assumed it would install 1.6.0_26-fcs which is in the repository, but: > > > cf3> -> Looking for (jdk,*,x86_64) > cf3> -> Matched name jdk > cf3> -> Matched arch x86_64 > cf3> -> Matched version * > cf3> -> Looking for (jdk,1.6.0_24-fcs,x86_64) > cf3> -> Matched name jdk > cf3> -> Matched arch x86_64 > cf3> -> Check for compatible versioning model in (1.6.0_24-fcs,1.6.0_24-fcs) > cf3> -> Verified that versioning models are compatible > cf3> -> Versions did not match > cf3> No installed packages matched (jdk,1.6.0_24-fcs,x86_64) > cf3> Checking if package (jdk,1.6.0_24-fcs,x86_64) is at the desired state > (installed=1,matched=0) > cf3> -> Package promises to refer to itself as "jdk" to the manager > cf3> Checking if latest available version is newer than installed... > cf3> Looking for an installed package older than (jdk,1.6.0_24-fcs,x86_64) > cf3> Found installed package (jdk,1.6.0_24-fcs,x86_64) > cf3> Installed package is up to date, not updating > > > The output confuses me completely, I'd still really like to see some > documentation as to how cfengine makes its decisions on packages. > > Thanks, > Sven > > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine > _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
