Description of problem:
Parameter and feature Conflicts field doesn't work like it should.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create two new parameters, one has the other in conflicts field
2. add both parameters on the same node
E.g. 'condor_configure_pool -a -n node -p NEW_PARAM1,NEW_PARAM2'
3. activate configuration changes
changes are accepted and configuration is activated
Conflict should be detected and activation should fail like when there are some not resolved dependency in configuration
similar scenario can be applied for features
Parameter conflict checking is now supported, and feature conflict checking is improved; these changes are upstream in commit e3700af.
Tested with (version):
RHEL5 x86_64,i386 - passed