Routes to an IP address managed by an aws-vpc-move-ip resource are missing in a Pacemaker cluster

Solution In Progress - Updated -

Issue

  • An ocf:heartbeat:aws-vpc-move-ip resource is in Started state, but I can't ping the VIP that it manages from the node where the resource is running.
  • The VIP's entry in the local route table is missing. For a VIP of 10.29.255.250, the following route table entry exists when I add the IP address manually with ip addr add, but it's not present when the aws-vpc-move-ip resource adds the address.
local 10.29.255.250 dev eth0 table local proto kernel scope host src 10.29.255.250

Environment

  • Red Hat Enterprise Linux 8 (with the High Availability Add-on)
    • RHEL 8.1: resource-agents-4.1.1-33.el8_1.1 or later
    • RHEL 8.2: resource-agents-4.1.1-44.el8_2.1 or later
  • Amazon Web Services (AWS)

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