Hide Forgot
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.
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): fence-virt-0.2.3-18.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. fence_virt -H xxxxx -t 1; echo $? 2. 3. Actual results: [root@virt-136 pengine]# fence_virt -H xxxxx -t 1; echo $? vmchannel connect: Connection timed out Failed to connect to 10.0.2.179:1229 0 Expected results: [root@virt-136 pengine]# fence_virt -H xxxxx -t 1; echo $? vmchannel connect: Connection timed out Failed to connect to 10.0.2.179:1229 0 <-- non-zero exit code should be displayed here Additional info:
This has already been fixed upstream in commit commit f7ccaa261a83505118b735067846f17bde12430c Author: Lon Hohberger <lon@users.sourceforge.net> Date: Tue Sep 20 11:40:39 2011 -0400 Fix static analysis errors Signed-off-by: Lon Hohberger <lon@users.sourceforge.net>
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. https://rhn.redhat.com/errata/RHBA-2015-1401.html