Bug 1126362
| Summary: | stonigh resources should stop only after other resources | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Fabio Massimo Di Nitto <fdinitto> | ||||
| Component: | pacemaker | Assignee: | Andrew Beekhof <abeekhof> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | cluster-qe <cluster-qe> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 7.0 | CC: | cluster-maint, dvossel | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1126880 (view as bug list) | Environment: | |||||
| Last Closed: | 2014-08-04 14:19:06 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1126880, 1126884 | ||||||
| Attachments: |
|
||||||
(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 ;)