[ClusterLabs] fence_scsi won't start

Marek "marx" Grac mgrac at redhat.com
Wed Apr 29 10:20:23 EDT 2015

On 04/29/2015 02:48 PM, Duncan Mortimer wrote:

>> Fence_scsi is using unique keys to identify machines that have reservations. These keys are either manually selected (key / --key on commandline) or automatically derived from cluster name & node name. But in order to find out it automatically, we need to know which node name should be impacted by fence/unfence action. Adding one of these option should help.
> Right, I’ve just had a look at this and couldn’t see how to either find out how I might specify the key or the node name in the pcs command that creates the stonith configuration and what documentation I could find on the matter suggested that if you didn’t specify them then, as you say, it should automatically generate the key. However, it does look like this is a known issue on RHEL 7.1 variants… https://access.redhat.com/solutions/1421063
I did not discover connection between these two issues. You are right 
with kbase.

It is fixed in upstream git repo; upstream release will be available 
next week; so RHEL should follow with next update too.


More information about the Users mailing list