An aws-vpc-move-ip resource logs "Cannot assign requested address" error during a successful start operation in a Pacemaker cluster
Issue
- An
ocf:heartbeat:aws-vpc-move-ipresource assigns its managed IP address, changes the routing table, and returns successfully, but it logs errors like the ones shown below.
Nov 9 07:56:14 ip-10-0-0-29 pacemaker-controld[4997]: notice: Initiating start operation aws-vip_start_0 locally on node1
Nov 9 07:56:14 ip-10-0-0-29 aws-vpc-move-ip(aws-vip)[6116]: INFO: EC2: Moving IP address 10.0.1.65 to this host by adjusting routing table rtb-01b4ea1ae0ec0a4d9
Nov 9 07:56:14 ip-10-0-0-29 aws-vpc-move-ip(aws-vip)[6116]: INFO: monitor: check routing table (API call) - rtb-01b4ea1ae0ec0a4d9
Nov 9 07:56:15 ip-10-0-0-29 aws-vpc-move-ip(aws-vip)[6116]: WARNING: IP 10.0.1.65 not assigned to running interface
Nov 9 07:56:15 ip-10-0-0-29 aws-vpc-move-ip(aws-vip)[6116]: INFO: EC2: Adjusting routing table and locally configuring IP address
Nov 9 07:56:17 ip-10-0-0-29 aws-vpc-move-ip(aws-vip)[6116]: WARNING: command failed, rc 2
Nov 9 07:56:17 ip-10-0-0-29 aws-vpc-move-ip(aws-vip)[6116]: INFO: monitor: check routing table (API call) - rtb-01b4ea1ae0ec0a4d9
Nov 9 07:56:18 ip-10-0-0-29 pacemaker-execd[4994]: notice: aws-vip_start_0[6116] error output [ RTNETLINK answers: Cannot assign requested address ]
Nov 9 07:56:18 ip-10-0-0-29 pacemaker-controld[4997]: notice: Result of start operation for aws-vip on node1: ok
Environment
- Red Hat Enterprise Linux 7 (with the High Availability Add-on)
- Red Hat Enterprise Linux 8 (with the High Availability Add-on)
- Amazon Web Services (AWS) EC2 instance as a cluster member
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
