Bug 1940097

Summary: awsvip: dont match similar IPs (RHEL7) [rhel-7.9.z]
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: unspecified Docs Contact:
Priority: unspecified    
Version: 7.8CC: agk, bperkins, cfeist, cluster-maint, fdinitto, jobaker, kpfleming, nwahl
Target Milestone: rcKeywords: Reopened, Triaged, ZStream
Target Release: 7.9Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: resource-agents-4.1.1-61.el7_9.17 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1939992 Environment:
Last Closed: 2023-01-24 10:09:15 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: 1939992    
Bug Blocks:    

Description Oyvind Albrigtsen 2021-03-17 15:44:57 UTC 
+++ This bug was initially created as a clone of Bug #1939992 +++

Description of problem:
Without this patch awsvip will match e.g. 10.0.0.200 if used with e.g. secondary_private_ip=10.0.0.20.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Create awsvip resource with 1 or more digit(s) removed from existing IP.

Actual results:
If you havent made the shorter IP it will get the status of e.g. 10.0.0.200.

Expected results:
Always returns the status of the correct IP.

Additional info:
https://github.com/ClusterLabs/resource-agents/pull/1626
Comment 18 errata-xmlrpc 2023-01-24 10:09:15 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-2023:0398