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 1125290 - fence_virt can return 0 on failure
Summary: fence_virt can return 0 on failure
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: fence-virt
Version: 6.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: cluster-qe@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-31 13:50 UTC by Jaroslav Kortus
Modified: 2015-07-22 07:32 UTC (History)
5 users (show)

Fixed In Version: fence-virt-0.2.3-19.el6
Doc Type: Bug Fix
Doc Text:
Previously, the fence-virt utility in some case incorrectly returned a zero exit code when it detected an error in processing a request. With this update, the static analysis errors that caused this problem have been fixed, and fence-virt now returns appropriate error codes if it detects an error.
Clone Of:
Last Closed: 2015-07-22 07:32:37 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1401 0 normal SHIPPED_LIVE fence-virt bug fix and enhancement update 2015-07-20 18:07:19 UTC

Description Jaroslav Kortus 2014-07-31 13:50:01 UTC
Description of problem:
fence_virt can return 0 even though it detected an error on processing the request

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

How reproducible:

Steps to Reproduce:
1. fence_virt -H xxxxx -t 1; echo $?

Actual results:
[root@virt-136 pengine]# fence_virt -H xxxxx -t 1; echo $?
vmchannel connect: Connection timed out
Failed to connect to

Expected results:
[root@virt-136 pengine]# fence_virt -H xxxxx -t 1; echo $?
vmchannel connect: Connection timed out
Failed to connect to
0 <-- non-zero exit code should be displayed here

Additional info:

Comment 2 Ryan McCabe 2014-09-15 15:16:29 UTC
This has already been fixed upstream in commit

commit f7ccaa261a83505118b735067846f17bde12430c
Author: Lon Hohberger <lon.net>
Date:   Tue Sep 20 11:40:39 2011 -0400

    Fix static analysis errors
    Signed-off-by: Lon Hohberger <lon.net>

Comment 7 errata-xmlrpc 2015-07-22 07:32:37 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.