The fence_aws fence agent fails to power on a node in a Pacemaker cluster

Solution Verified - Updated -

Issue

  • A node got fenced by fence_aws, but it was left in a powered off state instead of getting rebooted.
Feb 24 10:52:00 dn1sh4vm3 fence_aws: Status operation for EC2 instance i-xxxx returned state: RUNNING
Feb 24 10:52:00 dn1sh4vm3 fence_aws: Starting new HTTP connection (1): 169.254.169.254
Feb 24 10:52:01 dn1sh4vm3 fence_aws: Called StopInstance API call for i-xxxx
...
Feb 24 10:52:06 dn1sh4vm3 fence_aws: Status operation for EC2 instance i-xxxx returned state: STOPPING
...
Feb 24 10:52:38 dn1sh4vm3 fence_aws: Status operation for EC2 instance i-xxxx returned state: STOPPING
Feb 24 10:52:39 dn1sh4vm3 fence_aws: Status operation for EC2 instance i-xxxx returned state: STOPPED
Feb 24 10:52:39 dn1sh4vm3 fence_aws: Starting new HTTP connection (1): 169.254.169.254

Environment

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