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):
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
Service brings up the IP address and IP address collision occurs on the network.
/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.
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.
I would change the 'notice' to 'debug', otherwise the patch is good.
Would you like me to replace 'notice' to 'debug' and upload the modified one?
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.
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.