Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 78049 - fail-over interface not been removed
fail-over interface not been removed
Product: Red Hat Linux
Classification: Retired
Component: piranha (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike McLean
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2002-11-18 09:41 EST by Sébastien BONNET
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-11-18 09:41:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sébastien BONNET 2002-11-18 09:41:42 EST
Description of Problem:
It sometimes happens that a fail-over interface is not removed when pulse is 
stopped ("ifconfig ethN:X down" not run). This can create BIG problems when 
running with both a master and a backup director (resulting in having the VIP 
on both directors).

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

How Reproducible:
In my setup it was quite often, but it could be just 1 time out of 100 :(

Steps to Reproduce:
1. pulse -v -c /etc/sysconfig/ha/lvs.cf
2. wait a few seconds
3. service pulse stop
4. ifconfig might show the VIP whereas it should not

Actual Results:
VIP configured on director whereas service not running, or worse, running on 
backup director.

Expected Results:
VIP removed when pulse stoppped.

Additional Information:
The problem *seems* to be in pulse.c, in function deactivateFos. Swapping the 
HA_process termination and the VIP cleanup *seems* to be a fix. But not a real 
explaination :(
Comment 1 Mike McLean 2002-11-25 10:59:01 EST
Piranha's FOS functionality (though not piranha itself) is slated for removal. 
There are much better two node failover solutions out there, notably Red Hat
Cluster Manager.

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