RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1819021 - aws-vpc-move-ip leaves static routes
Summary: aws-vpc-move-ip leaves static routes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: resource-agents
Version: 8.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: 8.0
Assignee: Oyvind Albrigtsen
QA Contact: Brandon Perkins
URL:
Whiteboard:
Depends On:
Blocks: 1822250 1822251 1828895
TreeView+ depends on / blocked
 
Reported: 2020-03-31 00:38 UTC by Sherry Yu
Modified: 2020-11-04 02:19 UTC (History)
5 users (show)

Fixed In Version: resource-agents-4.1.1-47.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1822250 1822251 1828895 (view as bug list)
Environment:
Last Closed: 2020-11-04 02:19:10 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Sherry Yu 2020-03-31 00:38:31 UTC 
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:
Comment 3 Oyvind Albrigtsen 2020-04-06 06:59:00 UTC 
https://github.com/ClusterLabs/resource-agents/pull/1475/files
Comment 11 errata-xmlrpc 2020-11-04 02:19:10 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 (Low: resource-agents security and bug fix 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/RHSA-2020:4605
Note You need to log in before you can comment on or make changes to this bug.