Description of problem:
VIP doesn't start if ethernet link is down even if 'monitor_link' is set to '0'
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a service containing an IP resource.
2. Bring the target Ethernet link down (unplug the cable).
3. Try to start the resource on the node.
The resource won't start until the link is up.
If the 'monitor_link' parameter is set to '0' we are excepting that the cluster
will start the resource whether the status of the ethernet link.
A test script has been provide to a TAM customer.
Found it in attachment.
Created attachment 158609 [details]
VIP script modified
Created attachment 158946 [details]
Path for /usr/share/cluster/ip.sh to disable ethernet check with 'monitor_link=0'
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 the 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.