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.
DescriptionFabio Massimo Di Nitto
2014-04-06 18:10:39 UTC
Created attachment 883357[details]
crm_report
4 nodes cluster.
Setup fencing
test fencing on one node manually:
# setup cluster nodes (all nodes):
pcs cluster setup --name demo rhel6-ha-node1 rhel6-ha-node2 rhel6-ha-node3 rhel6-ha-node4
pcs cluster start
# wait ~30 sec
pcs status
# setup fencing (from one node)
pcs stonith create virt-fencing fence_xvm op monitor interval=10s
(wait for fencing to be started and pcs status is all good)
## test fencing
pcs stonith fence rhel6-ha-node4
when node4 rejoins the cluster it is often stuck in pending. A pacemaker restart or node reboot is required to recover. It appears that the issue is not consistent as it doesn't happen everytime but "often".
Created attachment 883357 [details] crm_report 4 nodes cluster. Setup fencing test fencing on one node manually: # setup cluster nodes (all nodes): pcs cluster setup --name demo rhel6-ha-node1 rhel6-ha-node2 rhel6-ha-node3 rhel6-ha-node4 pcs cluster start # wait ~30 sec pcs status # setup fencing (from one node) pcs stonith create virt-fencing fence_xvm op monitor interval=10s (wait for fencing to be started and pcs status is all good) ## test fencing pcs stonith fence rhel6-ha-node4 when node4 rejoins the cluster it is often stuck in pending. A pacemaker restart or node reboot is required to recover. It appears that the issue is not consistent as it doesn't happen everytime but "often".