Bug 717259

Summary:	"Run Exclusive" field does not correspond to configuration values
Product:	Red Hat Enterprise Linux 6	Reporter:	Chris <chris.alexander>
Component:	luci	Assignee:	Ryan McCabe <rmccabe>
Status:	CLOSED DUPLICATE	QA Contact:	Cluster QE <mspqa-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	cluster-maint
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-28 17:27:56 UTC	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 Chris 2011-06-28 13:14:56 UTC

Description of problem:
The "Run Exclusive" checkbox on the Luci administration panel for a service group does not correspond to the configuration in that service group's entry in the cluster.conf file.

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


How reproducible:
Easily

Steps to Reproduce:
1. Create a service in /etc/cluster/cluster.conf that is not run exclusive (i.e. exclusive="0" in its <service> tag)
2. Load service in Luci interface
3. Observe that "Run exclusive" checkbox is ticked where it should not
  
Actual results:
Checkbox is ticked when it should not be
When you modify the service in some way and Luci re-writes the configuration value, it takes the value of the checkbox, which often causes previously non-exclusive services to become exclusive services if you forget to uncheck the tickbox before you save the service changes.

Expected results:
Checkbox and configuration file remain in sync

Additional info:

Comment 2 Ryan McCabe 2011-06-28 17:27:56 UTC


*** This bug has been marked as a duplicate of bug 708205 ***