Red Hat Bugzilla – Bug 622562
Need to add support for unfencing conf. generation for SAN fencing agents and fence_scsi
Last modified: 2011-05-19 09:56:18 EDT
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.
This should be fixed as of commit http://git.fedorahosted.org/git?p=luci.git;a=commit;h=847508ae4483685d3eb59ed47433c02562c6bf0f
Following (storage) fence devices are affected, listed together with
appropriate action parameter for unfencing:
* brocade - enable
* mcdata - enable
* scsi - on
* sanbox2 - enable
(In reply to comment #1)
Only giving to know that a new bug in committed solution was found: bug #634126.
(In reply to comment #3)
Bug #634126 should be fixed.
*** Bug 634126 has been marked as a duplicate of this bug. ***
additionally http://git.fedorahosted.org/git/?p=luci.git;a=commit;h=bae8f42cb56d2e01e1d55f8f954cef4e7c3401b6 is needed here.
Created attachment 452754 [details]
Patch with all necessary fixes
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.
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.
fix verified in luci-0.23.0-12.el6
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.