Bug 1425835
| Summary: | NovaEvacuate should be able to fence the node when the node is off | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Chen <cchen> |
| Component: | resource-agents | Assignee: | Oyvind Albrigtsen <oalbrigt> |
| Status: | CLOSED DUPLICATE | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | agk, cluster-maint, fdinitto, jruemker, mschuppe |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-07-13 13:28:35 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: | |||
*** This bug has been marked as a duplicate of bug 1305549 *** |
Description of problem: NovaEvacuate should fence the compute node immediately when the node is off fence_compute will return 2 instead of 0 if the node's status is OFF. So we shouldn't wait for the compute node to completely come online but fence it when we lost the remote node connection. ocf_log notice "Initiating evacuation of $node" fence_compute ${fence_options} -o status -n ${node} - if [ $? != 0 ]; then + if [ $? != 0 -a $? != 2 ]; then ocf_log info "Nova does not know about ${node}" # Dont mark as no because perhaps nova is unavailable right now continue If I don't add a return code 2, then you will notice "Initiating evacuation of $node" will keep being output in the corosync.log. Version-Release number of selected component (if applicable): OSP10 instance HA How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: