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.
Bug 1287303 - [NovaEvacuate] Fabric fencing devices do not support reboot action
Summary: [NovaEvacuate] Fabric fencing devices do not support reboot action
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: Asaf Hirshberg
Depends On: 1287301
Blocks: 1185030 1304019
TreeView+ depends on / blocked
Reported: 2015-12-01 22:46 UTC by Andrew Beekhof
Modified: 2016-11-03 23:59 UTC (History)
7 users (show)

Fixed In Version: resource-agents-3.9.5-55.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1304019 (view as bug list)
Last Closed: 2016-11-03 23:59:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2174 0 normal SHIPPED_LIVE resource-agents bug fix and enhancement update 2016-11-03 13:16:36 UTC

Description Andrew Beekhof 2015-12-01 22:46:28 UTC
Description of problem:

We are changing the way fence_compute advertises itself in Bug #1287301, as a result it will no longer support the 'reboot' action causing evacuations to fail.

We need to change the action to 'off'.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Cause a compute node failure

Actual results:

NovaEvacuate's call to fence_compute fails with:

Failed: Unrecognised action 'reboot'

Expected results:

Call passes

Additional info:

  --- /usr/lib/ocf/resource.d/openstack/NovaEvacuate.orig    2015-11-30 21:53:57.868660753 -0500
+++ /usr/lib/ocf/resource.d/openstack/NovaEvacuate    2015-11-30 21:54:40.564659764 -0500
@@ -198,7 +193,7 @@
         return $OCF_SUCCESS
-        fence_compute ${fence_options} -o reboot -n $node
+        fence_compute ${fence_options} -o off -n $node
         if [ $rc = 0 ]; then

Comment 2 Oyvind Albrigtsen 2015-12-08 08:04:52 UTC

Comment 12 Asaf Hirshberg 2016-03-08 08:40:52 UTC
Verified on RHEL-OSP director 8.0 puddle - 2016-03-03.1

[heat-admin@overcloud-controller-0 ~]$ rpm -qa |grep resource-agents
[heat-admin@overcloud-controller-0 ~]$ cat /usr/lib/ocf/resource.d/openstack/NovaEvacuate |grep -n fence_compute
201:	    fence_compute ${fence_options} -o off -n $node
[heat-admin@overcloud-controller-0 ~]$

Comment 14 errata-xmlrpc 2016-11-03 23:59:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.