fence_vmware_soap fails with "Unable to connect/login to fencing device" when FIPS is enabled on a RHEL 8 Pacemaker cluster node

Solution In Progress - Updated -

Issue

  • When FIPS is enabled, fence_vmware_soap fails immediately as shown below.
# fence_vmware_soap -a <addr> -l <username> -p <password> --ssl-insecure -o list
2021-01-28 11:43:07,219 ERROR: Unable to connect/login to fencing device
  • The fence_vmware_soap command fails with a connection error, and tcpdump doesn't show any outbound packets destined for the vCenter or ESXi host.

Environment

  • Red Hat Enterprise Linux 8 (with the High Availability Add-on)

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

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content