RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

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