Bug 1828895

Summary: aws-vpc-move-ip leaves static routes (RHEL7)
Product: Red Hat Enterprise Linux 7 Reporter: Oyvind Albrigtsen <oalbrigt>
Component: resource-agentsAssignee: Oyvind Albrigtsen <oalbrigt>
Status: CLOSED ERRATA QA Contact: Brandon Perkins <bperkins>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.8CC: agk, bperkins, cfeist, cluster-maint, fdinitto
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: resource-agents-4.1.1-54.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1819021 Environment:
Last Closed: 2020-09-29 19:17:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1819021    
Bug Blocks: 1822250, 1822251    

Description Oyvind Albrigtsen 2020-04-28 14:30:33 UTC 
+++ This bug was initially created as a clone of Bug #1819021 +++

Description of problem:

Resource of aws-vpc-move-ip leaves a static routing entry even after the resource has failed over to the other cluster node.

Version-Release number of selected component (if applicable):
This issue has been observed on RHEL 8.0 with the following version. 
Name         : resource-agents
Version      : 4.1.1
Release      : 33.el8
Architecture : x86_64

How reproducible:
Reproducible in AWS environment

Steps to Reproduce:
1. Create a resource of aws-vpc-move-ip for OverlayIP. 

2. Wait till a static entry is created in the routing table. For example the virtual hostname is r8s4ascs.

[root@rhel8-node1 ~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         ip-10-0-1-1.ec2 0.0.0.0         UG    100    0        0 eth0
10.0.1.0        0.0.0.0         255.255.255.0   U     100    0        0 eth0
r8s4ascs        0.0.0.0         255.255.255.255 UH    100    0        0 eth0

3. Move the resource to the other cluster node, note that on the previous node the static route is still in the routing table.

Actual results:
The previous node still has a static route in the routing table
[root@rhel8-node1 ~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         ip-10-0-1-1.ec2 0.0.0.0         UG    100    0        0 eth0
10.0.1.0        0.0.0.0         255.255.255.0   U     100    0        0 eth0
r8s4ascs        0.0.0.0         255.255.255.255 UH    100    0        0 eth0

Expected results:
The route entry should be gone.

Additional info:

--- Additional comment from Oyvind Albrigtsen on 2020-04-06 08:59:00 CEST ---

https://github.com/ClusterLabs/resource-agents/pull/1475
Comment 6 errata-xmlrpc 2020-09-29 19:17:04 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (resource-agents bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3853