Pacemaker Resource showing as "unrunnable start (blocked)" for each cluster resource

SUSE Linux Enterprise Extensions SUSE Linux Enterprise Server
1

[{“insert”:"OS and Pacemaker Versions:
PRETTY_NAME=“SUSE Linux Enterprise Server 12 SP4”
CPE_NAME=“cpe:\/o:suse:sles_sap:12:sp4”\

pacemakerd --version\

Pacemaker 1.1.19+20181105.ccd6b5b10-3.16.1\

corosync -v\

Corosync Cluster Engine, version ‘2.3.6’
When cluster resources are running on glbgvldbies01, everything is fine, but when glbgvldbies02 is rebooted or down for some reason, the resource are not able to start on glbgvldbies02, We are getting the following error
"},{“insert”:{“embed-external”:{“data”:{“url”:“https:\/\/forums.suse.com\/uploads\/742\/E5AYI75RVUBP.txt”,“name”:“crm_config.txt”,“type”:“text\/plain”,“size”:1834,“mediaID”:359,“dateInserted”:“2020-05-12T15:00:43+00:00”,“insertUserID”:44760,“foreignType”:“embed”,“foreignID”:44760,“embedType”:“file”,“format”:null,“bodyRaw”:null},“loaderData”:{“type”:“file”,“file”:[],“progressEventEmitter”:{“listeners”:[null]}}}}},{“insert”:{“embed-external”:{“data”:{“url”:“https:\/\/forums.suse.com\/uploads\/518\/CMBW14SOQSH2.zip”,“name”:“pacemakerlog.zip”,“type”:“application\/x-zip-compressed”,“size”:137690,“mediaID”:360,“dateInserted”:“2020-05-12T15:01:55+00:00”,“insertUserID”:44760,“foreignType”:“embed”,“foreignID”:44760,“embedType”:“file”,“format”:null,“bodyRaw”:null},“loaderData”:{“type”:“file”,“file”:[],“progressEventEmitter”:{“listeners”:[null]}}}}},{“insert”:"Resource showing as “unrunnable start (blocked)”

"}]

2

[{“insert”:"Typo:
When cluster resources are running on glbgvldbies01, everything is fine, but when “},{“attributes”:{“bold”:true},“insert”:“glbgvldbies01”},{“insert”:” is rebooted or down for some reason, the resource are not able to start on glbgvldbies02
"}]

3

[{“insert”:"Today we have observed few things
"},{“insert”:{“embed-external”:{“data”:{“recordID”:59988,“recordType”:“comment”,“body”:“

Typo:<\/p>

When cluster resources are running on glbgvldbies01, everything is fine, but when glbgvldbies01<\/strong> is rebooted or down for some reason, the resource are not able to start on glbgvldbies02<\/p>”,“bodyRaw”:[{“insert”:"Typo:
When cluster resources are running on glbgvldbies01, everything is fine, but when “},{“attributes”:{“bold”:true},“insert”:“glbgvldbies01”},{“insert”:” is rebooted or down for some reason, the resource are not able to start on glbgvldbies02
"}],“format”:“Rich”,“dateInserted”:“2020-05-13T01:59:38+00:00”,“insertUser”:{“userID”:44760,“name”:“Ramesh”,“photoUrl”:“https:\/\/secure.gravatar.com\/avatar\/20214cb5a0f23482e82ce50b31a6a2b4\/?default=https%3A%2F%2Fvanillicon.com%2F9766dde30745d694fe85a33fe20e75f5_200.png&rating=g&size=200”,“dateLastActive”:“2020-05-14T14:26:27+00:00”},“displayOptions”:{“showUserLabel”:false,“showCompactUserInfo”:true,“showDiscussionLink”:false,“showPostLink”:false,“showCategoryLink”:false,“renderFullContent”:false,“expandByDefault”:false},“url”:“https:\/\/forums.suse.com\/discussion\/comment\/59988#Comment_59988”,“embedType”:“quote”},“loaderData”:{“type”:“link”,“link”:“https:\/\/forums.suse.com\/discussion\/comment\/59988#Comment_59988”}}}},{“insert”:“We have observed few things from the today testing. Following are the steps:
“},{“attributes”:{“bold”:true},“insert”:“Step 1”},{“insert”:”: When we create kernel panic (on Node01) with the command “”},{“attributes”:{“bold”:true},“insert”:“echo ‘b’ > \/proc\/sysrq-trigger”},{“insert”:“” or “”},{“attributes”:{“bold”:true},“insert”:“echo ‘c’ > \/proc\/sysrq-trigger”},{“insert”:"” on the node where the resources are running, then the cluster detecting the change but unable to start any resources (except SBD) on other active node.
“},{“attributes”:{“bold”:true},“insert”:“Step 2”},{“insert”:”: As per the logs we can find the following errors:
pengine: info: LogActions: Leave stonith-sbd (Started node02)
pengine: notice: LogAction: * Start pri-javaiq (node02 ) due to unrunnable nfs_filesystem start (blocked)
pengine: notice: LogAction: * Start lb_health_probe (node02 ) due to unrunnable nfs_filesystem start (blocked)
pengine: notice: LogAction: * Start pri-ip_vip (node02 ) due to unrunnable nfs_filesystem start (blocked)
pengine: notice: LogAction: * Start nfs_filesystem (node02 ) blocked
“},{“attributes”:{“bold”:true},“insert”:“Step 3”},{“insert”:”: But when we execute “init 6” on the node (on which we have created ‘kernel panic’), surprisingly the resources on other node are starting and running successfully.

"}]