Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1693658 - aws-vpc-move-ip: enable --query flag in DescribeRouteTable API to avoid possible race condition
Summary: aws-vpc-move-ip: enable --query flag in DescribeRouteTable API to avoid possi...
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.7
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: Brandon Perkins
URL:
Whiteboard:
Depends On:
Blocks: 1693662
TreeView+ depends on / blocked
 
Reported: 2019-03-28 12:30 UTC by Cole Towsley
Modified: 2019-04-11 17:25 UTC (History)
5 users (show)

Fixed In Version: resource-agents-4.1.1-21.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1693662 (view as bug list)
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4016661 Upgrade None How to avoid a race condition with "grep" while parsing the results from AWS CLI ? 2019-03-28 17:13:52 UTC

Description Cole Towsley 2019-03-28 12:30:15 UTC
The initial issue is a possible race condition due to the use of grep parsing results from AWS CLI. A fix has been proposed and included upstream (https://github.com/ClusterLabs/resource-agents/pull/1269)


From the upstream git request:

"This is a proposed fix to avoid a race condition with "grep" while parsing the results from AWS CLI.

Currently, "grep" will match for IPs that don't belong tho the cluster resource. For example, if your cluster resource IP address is "192.168.1.1", "grep" will match "192.168.1.1*" (192.168.1.1,10,11,...,111).

This could have been fixed by a simple "grep -w" but we (AWS) thought it is more elegant to directly use the API to query for the IP.

I also included a debug log line."


Note You need to log in before you can comment on or make changes to this bug.