Description of problem: The SharedPort feature in the base-db does not depend upon anything, and as a result installing it on a group/node results in a non-functional config and no indication that Master is needed. The SharedPort feature should depend upon the Master feature. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The SharedPort feature now depends on Master. Fixed upstream on: BZ831709-SharedPort-adddep-Master
There are a few ways to test this: 1) Look at the details of the SharedPort feature in wallaby. In previous versions it had no dependency on the Master feature. With this change, Master is now listed as a dependency 2) Install SharedPort on a node/group by itself and activate. With the previous versions the activation would succeed, but the configuration on the node(s) would not be valid and condor would not start (no MASTER in DAEMON_LIST). With this change, the wallaby activation will fail because of a missing dependency on Master.
Reproduced with: wallaby-0.12.5-1.el5 # wallaby show-features SharedPort Console Connection Established... SharedPort name: "SharedPort" params: {"USE_SHARED_PORT"=>"True", "DAEMON_LIST"=>">= SHARED_PORT", "SHARED_PORT_DEBUG"=>"", "SHARED_PORT"=>"$(LIBEXEC)/condor_shared_port", "DAEMON_SOCKET_DIR"=>"$(RUN)"} depends: [] conflicts: [] included_features: [] You have new mail in /var/spool/mail/root
Retested on RHEL5/6 with: wallaby-0.16.1-2 # wallaby show-features SharedPort Console Connection Established... SharedPort name: "SharedPort" params: {"USE_SHARED_PORT"=>"TRUE", "DAEMON_SOCKET_DIR"=>"$(RUN)", "DAEMON_LIST"=>">= SHARED_PORT", "SHARED_PORT"=>"$(LIBEXEC)/condor_shared_port", "SHARED_PORT_DEBUG"=>""} depends: ["Master"] conflicts: [] included_features: [] annotation: "Enables shared port" The SharePort feature now depends on Master. >>> VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0564.html