Description of problem: When removing a feature using the condor_configure_node tool, it doesn't properly handle recursive dependencies. So, if Feature A is removed, Feature B depends on A, and Feature C depends on B, then only A and B will be removed and not C. Version-Release number of selected component (if applicable): 1.0-10 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The issue was in determining if a dependency existed in a comma separated list of dependencies. If a feature had only 1 dep then there wasn't a problem. If a feature had 2 deps (comma separated), then the tool wouldn't process the deps. This was only an issue when removing a feature. This will be fixed in 1.0-11
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0036.html