Bug 526647

Summary: Cluster IP resource does not deal with IP address collision possibility
Product: Red Hat Enterprise Linux 5 Reporter: Ferenc Antal <antalf>
Component: rgmanagerAssignee: Lon Hohberger <lhh>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 5.4CC: cluster-maint, edamato, szivan
Target Milestone: rc   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: rgmanager-2.0.52-1.22.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-30 08:49:39 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:
Attachments:
Description Flags
suggested patch for ip.sh to avoid IP address collisions none

Description Ferenc Antal 2009-10-01 09:37:41 UTC 
Description of problem:
Cluster IP resource brings up an IP address without prior checking. If the IP remains live on other cluster member it leads to IP address collision.

Version-Release number of selected component (if applicable):
rgmanager-2.0.52-1.el5

How reproducible:
Starting a cluster service with an IP resource while that IP address exists on the network.

Steps to Reproduce:
1. Create cluster service with IP resource
2. Bring up the same IP address manually on nodeB
3. Start the service on nodeA
  
Actual results:
Service brings up the IP address and IP address collision occurs on the network.

Expected results:
/usr/share/cluster/ip.sh should check an IP address presence before bringing up an IP address. If the IP address is responding it should block the service avoiding IP address collision.

Additional info:
Comment 1 Ferenc Antal 2009-10-16 08:32:44 UTC 
Created attachment 365025 [details]
suggested patch for ip.sh to avoid IP address collisions

This patch inserts ping check into ip.sh prior to IP address activation.
Comment 2 Lon Hohberger 2009-10-16 21:50:30 UTC 
I would change the 'notice' to 'debug', otherwise the patch is good.
Comment 3 Ferenc Antal 2009-10-22 08:45:00 UTC 
Would you like me to replace 'notice' to 'debug' and upload the modified one?
Comment 4 Lon Hohberger 2009-10-27 19:45:40 UTC 
No, it's fine.  If you're okay with that small change I will just commit the patch with the minor change with you as the author.
Comment 5 Lon Hohberger 2009-11-13 20:15:01 UTC 
http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=3ae5f5cea15c8198141308d0fc8443853c45faf4

http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=d767b979e3841b01d39e498e15ae72d446c12f78
Comment 8 errata-xmlrpc 2010-03-30 08:49:39 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0280.html