Bug 478894 - remote-configuration tool does not properly process deps for removal
remote-configuration tool does not properly process deps for removal
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid (Show other bugs)
1.0
All Linux
medium Severity medium
: 1.1
: ---
Assigned To: Robert Rati
Jeff Needle
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-05 16:27 EST by Robert Rati
Modified: 2009-02-04 11:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-02-04 11:06:18 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Robert Rati 2009-01-05 16:27:57 EST
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:
Comment 1 Robert Rati 2009-01-05 17:33:04 EST
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
Comment 4 errata-xmlrpc 2009-02-04 11:06:18 EST
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

Note You need to log in before you can comment on or make changes to this bug.