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.
If SAN fence devices (or SCSI fencing) are used, fence configuration must be performed after upgrading to a version of luci containing a fix for this bug. If SAN fencing is configured prior to upgrading luci, the unfence configuration will not be written to the cluster configuration file, which will cause fencing to not operate correctly. If this is the case, after upgrading luci, configuration for SAN fence agents must be removed and redone.
Description of problem:
Luci presently does not allow the user to configure unfencing which means that the SAN fencing agents and fence_scsi cannot be unfenced on system boot.
Need to add an option that is enabled by default for all of the SAN fence configuration pages to enable unfencing functionality.
Comment 1Jan Pokorný [poki]
2010-08-13 17:14:27 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
If SAN fence devices (or SCSI fencing) are used, fence configuration must be performed after upgrading to a version of luci containing a fix for this bug. If SAN fencing is configured prior to upgrading luci, the unfence configuration will not be written to the cluster configuration file, which will cause fencing to not operate correctly. If this is the case, after upgrading luci, configuration for SAN fence agents must be removed and redone.
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