On 06/03/12 13:43, no-re...@cfengine.com wrote: > > Package managers can act in unexpected and unwanted ways. Look at the > verbose output of the agent to see what is going on. >
I've been through the verbose output at some length - the package manager seems to be doing exactly what it's supposed to - all the packages I've scheduled for installation get installed. Specifically, I'm using this to install nagios check agents, and what I see is that each section (both the global, and the dell specific) sees that packages have been requested that aren't installed, and selects them for presentation to the package manager. On a Dell server, what I get is:- cf3> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> cf3> -> Deletion schedule... cf3> -> Addition schedule... cf3> Execute scheduled package addition cf3> Command prefix: /usr/bin/aptitude --assume-yes install cf3> Executing /usr/bin/aptitude --assume-yes install check-openmanage nagi... cf3> Q:aptitude --assume-ye ...:Reading package lists... cf3> Q:aptitude --assume-ye ...:Building dependency tree... cf3> Q:aptitude --assume-ye ...:Reading state information... cf3> Q:aptitude --assume-ye ...:Reading extended state information... cf3> Q:aptitude --assume-ye ...:Initializing package states... cf3> Q:aptitude --assume-ye ...:Reading task descriptions... cf3> Q:aptitude --assume-ye ...:The following NEW packages will be installed: cf3> Q:aptitude --assume-ye ...: check-openmanage libmysqlclient16{a} libpq5{a} libradiusclient-ng2{a} cf3> Q:aptitude --assume-ye ...: mysql-common{a} nagios-nrpe-server nagios-plugins nagios-plugins-basic{a} cf3> Q:aptitude --assume-ye ...: nagios-plugins-standard{a} It's clearly installing all the packages I'd expect. However, at the end of the installation phase, the verbose log shows this:- cf3> -> Finished command related to promiser "check-openmanage" -- succeeded cf3> ?> defining promise result class install_omcheck cf3> Bulk package schedule execution ok for check-openmanage (outcome cannot be promised by cf-agent) cf3> Bulk package schedule execution ok for nagios-nrpe-server (outcome cannot be promised by cf-agent) cf3> Bulk package schedule execution ok for nagios-plugins (outcome cannot be promised by cf-agent) I would have expected two classes to be defined, not just the one. However, what I guess is happening is that as the package installation operations are being lumped together, only a single "install" command is being executed, so I'm seeing the class definitions get "overwritten" somehow, and only the last class ever gets defined? My thought at the moment is to rewrite this differently, so the class gets defined according to a file: promise on something I expect to be in the package, but it's a bit ugly, and I was wondering if there's a better way? Mike _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine