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-08-04 09:32:47 UTC
Created attachment 923818[details]
crm_report
I was randomly monitoring crm_mon -r while issuing a pcs cluster stop --all on another node and I noticed that all stonith resources were stopped before other resources.
this could potentially be an issue if a resource fail to stop and we need to complete recovery of the node to shutdown everything else properly.
I attached the crm_report just in case it was a visual artifact ;)
(In reply to Fabio Massimo Di Nitto from comment #0)
> Created attachment 923818[details]
> crm_report
>
> I was randomly monitoring crm_mon -r while issuing a pcs cluster stop --all
> on another node and I noticed that all stonith resources were stopped before
> other resources.
This should be fine.
As long as we haven't gone in and explicitly disabled a fencing device or setup constraints in a way that prevent a fencing device from executing on a node, it doesn't matter if crm_mon shows that the device is down or not. The device will still be available to stonith.
Think of all stonith resources as a special type of clone resource. We only show one instance of the stonith device running, and that's the location we expect to execute the stonith operation for that device. but... if the stonith device is not placed anywhere or the device's location is the target of the fencing operation, we'll attempt to use the same device on another node.
-- Vossel
>
> this could potentially be an issue if a resource fail to stop and we need to
> complete recovery of the node to shutdown everything else properly.
>
> I attached the crm_report just in case it was a visual artifact ;)
Created attachment 923818 [details] crm_report I was randomly monitoring crm_mon -r while issuing a pcs cluster stop --all on another node and I noticed that all stonith resources were stopped before other resources. this could potentially be an issue if a resource fail to stop and we need to complete recovery of the node to shutdown everything else properly. I attached the crm_report just in case it was a visual artifact ;)