Fencing in RHEL 6 with fence_vmware_soap fails with "error from agent" when done automatically by cluster or using fence_node, but succeeds from command line

Solution Unverified - Updated -

Issue

  • When the cluster tries to fence a node with fence_vmware_soap, or I run fence_node, it fails with "error from agent":
Feb  7 09:14:40 node1 fenced[12763]: fencing node  node3
Feb  7 09:14:40 node1 abrt: detected unhandled Python exception in '/usr/sbin/fence_vmware_soap'
Feb  7 09:14:40 node1 fenced[12763]: fence node3 dev 0.0 agent fence_vmware_soap result: error from agent
Feb  7 09:14:40 node1 fenced[12763]: fence node3 failed

If I run fence_vmware_soap from the command line with the same parameters, it works fine

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add on
  • One or more nodes configured to use fence_vmware_soap in /etc/cluster/cluster.conf
  • SELinux in enforcing mode (selinux=enforcing in /etc/sysconfig/selinux)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In