fence_vmware_soap does not function correctly against vSphere 5 SOAP API

Solution verified - Updated on

Request a new translation or translation update

A translation for your language preference does not exist. Click below to request a translation for your selected language.

Submit request

Issue

  • Custer member hung due to failed fencing after upgrading to VSphere5.
  • fence_vmware_soap does not function correctly against vSphere 5 SOAP API and a backtrace occurs when the command is run:
# fence_vmware_soap -o list -a <vCenter> -l <logon&
...

Subscriber Exclusive Content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content