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.

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:

*** This bug has been marked as a duplicate of bug 1305549 ***