Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionJan Pokorný [poki]
2010-09-14 20:13:31 UTC
Description of problem:
In connection with bug #633567, it was discovered that Luci currently treats "nodename" parameter for fence_scsi fence agent as "global" per its device instance (i.e. it is by "fencedevice" xml-node in cluster.conf), instead of node-local one (i.e. by "device" xml-node).
In addition, there are two related problems that should be fixed as well:
A. on RHEL5(4), this parameter served cluster for specific reason and it was expected (and as I verified, this rule had no exception) that its value is the same as the name of the respective node ("clusternode" xml-node, attribute "name"), see http://sources.redhat.com/cluster/wiki/SCSI_FencingConfig_RHEL5
- Luci currently handles this parameter as user-configurable, which can lead to problems when the stated rule is broken -> this logic should be applied automatically in silence without giving user a chance to modify it in Luci
B. for RHEL6-based cluster, setting "nodename" parameter can be omitted, because in this case (and only in this case!), mentioned rule is applied implicitly by the logic of fence components (fenced)
- to keep cluster.conf as "clean" as possible, it would be a good idea to choose omitting this parameter (note: once "nodename" parameter present by "device" xml-node under "fence" - "method" section, it ought to be present also by "device" xml-node under "unfence" section for particular node)
Comment 3Jan Pokorný [poki]
2010-09-15 21:33:18 UTC
fix verified in luci-0.23.0-4
the <fencedevice> name parameter is set during element creation, and matches the <fence><method><device name=""> parameter selected from a drop-down list.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0655.html