Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Creating a cluster resource with pcs using aws-vpc-move-ip, the local route for the overlay IP is being removed.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux release 8.1 - package resource-agents >= 4.1.1-33.el8_1.1
Red Hat Enterprise Linux release 8.2 - pacakge resource-agents >= 4.1.1-44.el8_2.1
How reproducible:
On AWS EC2, launch an instance from AMI Red Hat Enterprise Linux for SAP with HA and Update Services 8.1 or 8.2. Install pacemaker, and configure an overlay IP using aws-vpc-move-ip. From the node itself, try to ping or establish any TCP connection to a listening port. It will time out.
Steps to Reproduce:
1. On AWS cloud, launch an EC2 instance from Marketplace AMI Red Hat Enterprise Linux for SAP with HA and Update Services 8.1 or 8.2
2. Install pacemaker, and configure a new resource in the cluster with aws-vpc-move-ip.
3. When the overlay IP comes up on the node, attempt to ping or open a TCP connection to a listening port on the new IP (from the node itself).
Actual results:
There's no response, time out.
Expected results:
Traffic to flow accordingly.
Additional info:
Looking to the script /usr/lib/ocf/resource.d/heartbeat/aws-vpc-move-ip, at the end of the function ec2ip_get_and_configure(), the following lines are removing the local route-entries after adding the local IP:
---
# delete remaining route-entries if any
ip route show to exact ${OCF_RESKEY_ip}/32 dev $OCF_RESKEY_interface | xargs -r ip route delete
ip route show table local to exact ${OCF_RESKEY_ip}/32 dev $OCF_RESKEY_interface | xargs -r ip route delete
---
I believe the lines above were supposed to be inside the function ec2ip_drop() per upstream code [1].
Reference:
[1] https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/aws-vpc-move-ip
Description of problem: Creating a cluster resource with pcs using aws-vpc-move-ip, the local route for the overlay IP is being removed. Version-Release number of selected component (if applicable): Red Hat Enterprise Linux release 8.1 - package resource-agents >= 4.1.1-33.el8_1.1 Red Hat Enterprise Linux release 8.2 - pacakge resource-agents >= 4.1.1-44.el8_2.1 How reproducible: On AWS EC2, launch an instance from AMI Red Hat Enterprise Linux for SAP with HA and Update Services 8.1 or 8.2. Install pacemaker, and configure an overlay IP using aws-vpc-move-ip. From the node itself, try to ping or establish any TCP connection to a listening port. It will time out. Steps to Reproduce: 1. On AWS cloud, launch an EC2 instance from Marketplace AMI Red Hat Enterprise Linux for SAP with HA and Update Services 8.1 or 8.2 2. Install pacemaker, and configure a new resource in the cluster with aws-vpc-move-ip. 3. When the overlay IP comes up on the node, attempt to ping or open a TCP connection to a listening port on the new IP (from the node itself). Actual results: There's no response, time out. Expected results: Traffic to flow accordingly. Additional info: Looking to the script /usr/lib/ocf/resource.d/heartbeat/aws-vpc-move-ip, at the end of the function ec2ip_get_and_configure(), the following lines are removing the local route-entries after adding the local IP: --- # delete remaining route-entries if any ip route show to exact ${OCF_RESKEY_ip}/32 dev $OCF_RESKEY_interface | xargs -r ip route delete ip route show table local to exact ${OCF_RESKEY_ip}/32 dev $OCF_RESKEY_interface | xargs -r ip route delete --- I believe the lines above were supposed to be inside the function ec2ip_drop() per upstream code [1]. Reference: [1] https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/aws-vpc-move-ip