Bug 614430

Summary:	Remote configuration Conflicts field
Product:	Red Hat Enterprise MRG	Reporter:	Lubos Trilety <ltrilety>
Component:	wallaby-utils	Assignee:	Will Benton <willb>
Status:	CLOSED ERRATA	QA Contact:	Lubos Trilety <ltrilety>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	Development	CC:	matt, willb
Target Milestone:	1.3
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lubos Trilety 2010-07-14 13:38:36 UTC

Description of problem:
Parameter and feature Conflicts field doesn't work like it should.

Version-Release number of selected component (if applicable):
wallaby-0.6.1-2

How reproducible:
100%

Steps to Reproduce:
1. create two new parameters, one has the other in conflicts field
   E.g.
   NEW_PARAM1
   Dependencies:
   Conflicts:

   NEW_PARAM2
   Dependencies:
   Conflicts:
     NEW_PARAM1
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
  
Actual results:
changes are accepted and configuration is activated

Expected results:
Conflict should be detected and activation should fail like when there are some not resolved dependency in configuration

Additional info:
similar scenario can be applied for features

Comment 1 Will Benton 2010-07-19 22:30:49 UTC

Parameter conflict checking is now supported, and feature conflict checking is improved; these changes are upstream in commit e3700af.

Comment 2 Lubos Trilety 2010-08-09 13:28:18 UTC

Tested with (version):
wallaby-0.9.2-1

Tested on:
RHEL5 x86_64,i386  - passed

>>> VERIFIED