Bug 769798 - fence_vmare_soap is slower than fence_vmware
fence_vmare_soap is slower than fence_vmware
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: fence-agents (Show other bugs)
x86_64 Linux
high Severity high
: rc
: ---
Assigned To: Marek Grac
Cluster QE
: Patch, ZStream
Depends On:
Blocks: 836654 868183 872620
  Show dependency treegraph
Reported: 2011-12-22 04:56 EST by Timothy
Modified: 2014-06-30 07:36 EDT (History)
11 users (show)

See Also:
Fixed In Version: fence-agents-3.1.5-21.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 836654 868183 (view as bug list)
Last Closed: 2013-02-21 02:41:10 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 89183 None None None Never
Red Hat Knowledge Base (Article) 108933 None None None 2012-09-21 10:44:00 EDT

  None (edit)
Description Timothy 2011-12-22 04:56:57 EST
Description of problem:
My test shows that I have to wait approximately 15 Seconds where as when I use fence_vmware, I get a result immediately:

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

How reproducible:
# time fence_vmware_soap -o status -a -l vm_stonith -p '***pwd***' -v -U 4211b0a1-bb56-edc2-2c77-fc594ceab28f -u 443 -z
Status: ON
real    0m15.832s

# time fence_vmware -o status -a -l vm_stonith -p '***pwd***' -n "test1"
Status: ON
real    0m1.422s

Actual results:
fence_vmware_soap needs much more time to complete

Expected results:
answer time is in same range
Comment 21 Marek Grac 2012-10-25 05:07:45 EDT
Unit test:

Check if status is working correctly. It is possible to test if fencing response is better then in previous version but this is hard to measure. 

fence_vmware_soap -z -l LOGIN -p PASS -a IPADDR -n VMNAME
Comment 26 errata-xmlrpc 2013-02-21 02:41:10 EST
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.