I initially was using package_method "yum," which worked fine until my package 
list got too long ... looks like some buffer / cache fills up and breaks the 
process ( note "No package comp available." in the below, next item in list 
would be "compat-expat1" );

Q:yum -y install xymon ...:No package compat-gcc-34-c++.noarch available.
Q:yum -y install xymon ...:No package compat-gcc-34-c++.i686 available.
Q:yum -y install xymon ...:Package compat-gcc-34-c++-3.4.6-19.el6.x86_64 
already installed and latest version
Q:yum -y install xymon ...:No package comp available.
Q:yum -y install xymon ...:Nothing to do
Q:yum -y install xymon ...:

Breaking my list into two groups didn't fix the problem. I switched to 
package_method "yum_rpm," which worked fine for a while ... and then suddenly 
broke by deciding to only install the x86_64 version even when only i686 was 
specified for package_architectures. From looking at the verbose output, the 
architecture string is getting dropped;

Executing /usr/bin/yum -y install compat-expat1 compat-expat1 compat-e...

It's not the length of the package list this time, I've tested with a list of 
two packages. I'm aware of the bug relating to this that was fixed in v3.1.4, 
this is not that (I'm running 3.1.4, this has been working fine until a couple 
of days ago.) No changes to cfengine version or cfengine_stdlib.cf, I'm at a 
loss as to why this suddenly changed behavior.  

At this point I'm largely posting out of curiosity and confirming this in case 
anybody else is seeing it ... "packages:" has proved to be largely a 
labor-generator for me, so I'm going back to doing the bulk package install in 
a kickstart post script, which I was doing with cf2. I was hoping to have cf3 
manage the whole thing to keep me from having two lists to manage as we added 
new packages, but that seems like a lot less work at this point. 

We're running cf3 exclusively on RHEL6 at the moment.
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine

Reply via email to