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.

+++ This bug was initially created as a clone of Bug #906016 +++

Currently, luci is too liberate in terms of what configuration can be
achieved using it.

This bugs is to closely examine the semantically correct parameters
that can be used in conjuction with particular fence agents either
in the form of fence devices defined or respective per-node instances.

Note that partially, this is already captured in cluster.rng
(or obtainable from the same source as fence-agent related parts of
cluster.rng are generated), however:

1/ I am not sure about clear distinction of categories arising
   from a 2D matrix with axis can-be-at-device and can-be-at-instance

2/ with pure cluster.rng, we cannot prevent from fence_brocade instance
   having a "delay" attribute (see [bug 815666 comment 15]).


When the exact situation is mapped, the result of this RFE will be
less space for semantically incorrect configuration as the correct
attributes and either fence devices and instances will be enforced.

re: 2/ fence_brocade case was apparently a mere example

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.