Bug 769798

Summary:	fence_vmare_soap is slower than fence_vmware
Product:	Red Hat Enterprise Linux 6	Reporter:	Timothy <supertimothy>
Component:	fence-agents	Assignee:	Marek Grac <mgrac>
Status:	CLOSED ERRATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.2	CC:	amoralej, ccaulfie, cluster-maint, cww, djansa, isabel.rangel, mjuricek, pzimek, rfreire, sbradley, yowang
Target Milestone:	rc	Keywords:	Patch, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	fence-agents-3.1.5-21.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	836654 868183 (view as bug list)		Environment:
Last Closed:	2013-02-21 07:41:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	836654, 868183, 872620

Description Timothy 2011-12-22 09:56:57 UTC

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):
3.1.5-10.el6

How reproducible:
# time fence_vmware_soap -o status -a 10.1.1.1 -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 10.1.1.1 -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 09:07:45 UTC

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 07:41:10 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.

http://rhn.redhat.com/errata/RHBA-2013-0286.html