Tested on RHEL6, x86_64 with: qpid-java-common-0.10-4.el6.noarch qpid-java-example-0.10-4.el6.noarch wallaby-utils-0.10.5-4.el6.noarch condor-qmf-7.6.1-0.4.el6.x86_64 qpid-cpp-client-0.10-3.el6.x86_64 qpid-cpp-client-ssl-0.10-3.el6.x86_64 qpid-cpp-server-ssl-0.10-3.el6.x86_64 qpid-cpp-server-store-0.10-3.el6.x86_64 ruby-wallaby-0.10.5-4.el6.noarch qpid-java-client-0.10-4.el6.noarch wallaby-0.10.5-4.el6.noarch qpid-java-jca-0.10-4.el6.noarch condor-classads-7.6.1-0.4.el6.x86_64 python-condorutils-1.5-3.el6.noarch condor-wallaby-tools-4.0-6.el6.noarch condor-aviary-7.6.1-0.4.el6.x86_64 condor-kbdd-7.6.1-0.4.el6.x86_64 ruby-qpid-qmf-0.10-6.el6.x86_64 condor-wallaby-base-db-1.12-1.el6.noarch qpid-cpp-server-0.10-3.el6.x86_64 qpid-cpp-client-rdma-0.10-3.el6.x86_64 qpid-cpp-client-devel-0.10-3.el6.x86_64 python-qpid-qmf-0.10-6.el6.x86_64 qpid-cpp-server-rdma-0.10-3.el6.x86_64 qpid-cpp-server-cluster-0.10-3.el6.x86_64 rh-qpid-cpp-tests-0.10-3.el6.x86_64 qpid-tools-0.10-3.el6.noarch qpid-cpp-server-devel-0.10-3.el6.x86_64 qpid-cpp-client-devel-docs-0.10-3.el6.noarch condor-7.6.1-0.4.el6.x86_64 python-wallabyclient-4.0-6.el6.noarch condor-vm-gahp-7.6.1-0.4.el6.x86_64 condor-debuginfo-7.6.1-0.4.el6.x86_64 condor-wallaby-client-4.0-6.el6.noarch python-qpid-0.10-1.el6.noarch qpid-qmf-0.10-6.el6.x86_64 ruby-qpid-0.7.946106-2.el6.x86_64 qpid-cpp-server-xml-0.10-3.el6.x86_64 qpid-tests-0.10-1.el6.noarch The triggerd object is available via synchronous qmf console: # grep -i condortrigger qmf.out com.redhat.grid:condortriggerservice:triggerd@hostname (0-12-1-0-org.apache.qpid.broker:binding:org.apache.qpid.broker:exchange:qmf.default.direct,org.apache.qpid.broker:queue:qmfagent-75a222b5-dd41-4caa-a82e-5163842789d8,com.redhat.grid:condortriggerservice:triggerd@hostname) bindingKey com.redhat.grid:condortriggerservice:triggerd@hostname There is no condortriggerservice object available over qpid-tool: qpid: list Summary of Objects by Type: Package Class Active Deleted ======================================================= com.redhat.grid scheduler 1 0 com.redhat.grid slot 1 0 org.apache.qpid.broker binding 47 33 org.apache.qpid.broker subscription 14 15 com.redhat.grid master 1 0 org.apache.qpid.broker queue 14 15 org.apache.qpid.broker broker 1 0 org.apache.qpid.broker system 1 0 com.redhat.grid negotiator 1 0 com.redhat.grid submission 244 0 org.apache.qpid.broker connection 10 20 org.apache.qpid.broker session 10 3 com.redhat.grid jobserver 2 0 org.apache.qpid.broker exchange 8 0 com.redhat.grid submitter 1 0 org.apache.qpid.broker vhost 1 0 org.apache.qpid.broker agent 1 0 com.redhat.grid collector 1 0 # condor_trigger_config -i `hostname` Connecting to broker 'hostname'... No condor trigger service found Depended bug must be solved to retest issue on RHEL6 - QMF data query from synchronous (qmf_list_objects) and asynchronous (qpid-tool) console gives different results
Fixed in: # rpm -qa | egrep '(qpid|sesame|matahari)' | sort python-qpid-0.10-1.el6.noarch python-qpid-qmf-0.10-7.el6.x86_64 qpid-cpp-client-0.10-5.el6.x86_64 qpid-cpp-client-devel-0.10-5.el6.x86_64 qpid-cpp-client-devel-docs-0.10-5.el6.noarch qpid-cpp-client-rdma-0.10-5.el6.x86_64 qpid-cpp-client-ssl-0.10-5.el6.x86_64 qpid-cpp-server-0.10-5.el6.x86_64 qpid-cpp-server-cluster-0.10-5.el6.x86_64 qpid-cpp-server-devel-0.10-5.el6.x86_64 qpid-cpp-server-rdma-0.10-5.el6.x86_64 qpid-cpp-server-ssl-0.10-5.el6.x86_64 qpid-cpp-server-store-0.10-5.el6.x86_64 qpid-cpp-server-xml-0.10-5.el6.x86_64 qpid-java-client-0.10-6.el6.noarch qpid-java-common-0.10-6.el6.noarch qpid-java-example-0.10-6.el6.noarch qpid-java-jca-0.10-6.el6.noarch qpid-qmf-0.10-7.el6.x86_64 qpid-tests-0.10-1.el6.noarch qpid-tools-0.10-4.el6.noarch rh-qpid-cpp-tests-0.10-5.el6.x86_64 ruby-qpid-0.7.946106-2.el6.x86_64 ruby-qpid-qmf-0.10-7.el6.x86_64 sesame-debuginfo-0.10-1.el6.x86_64 qpid: list Summary of Objects by Type: Package Class Active Deleted =============================================================== com.redhat.grid slot 1 0 org.apache.qpid.broker binding 63 0 org.apache.qpid.broker subscription 21 0 com.redhat.grid master 1 0 org.apache.qpid.broker queue 21 0 org.apache.qpid.broker broker 1 0 org.apache.qpid.broker system 1 0 com.redhat.grid negotiator 1 0 com.redhat.grid submission 243 0 org.apache.qpid.broker connection 11 0 org.apache.qpid.broker session 11 0 org.apache.qpid.broker exchange 8 0 com.redhat.grid jobserver 1 0 com.redhat.grid condortriggerservice 1 0 org.apache.qpid.broker vhost 1 0 org.apache.qpid.broker agent 1 0 com.redhat.grid collector 1 0 >>> VERIFIED
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: C: Added the ability to detect node expected to be in the pool but aren't found (absent nodes) C: Absent nodes were not detected C: The condor_triggerd can detect absent nodes if ENABLE_ABSENT_NODES_DETECTION is set to TRUE R: If absent node detection is enabled, the condor_triggerd will raise an event for each node configured in wallaby for which a master qmf object is not detected Release Note Entry: Previously, _triggerd's C++ Console interface in Condor could not detect and report absent nodes because ENABLE_ABSENT_NODES_DETECTION was set to FALSE as a default. The ENABLE_ABSENT_NODES_DETECTION is now set to TRUE as a default in Condor, which allows _triggerd to raise an event for each node in wallaby that does not have a corresponding master qmf object.
Technical note can be viewed in the release notes for 2.0 at the documentation stage here: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2.0/html-single/MRG_Release_Notes/index.html#tabl-MRG_Release_Notes-GRID_Update_Notes-RHM_Known_Issues