+++ This bug was initially created as a clone of Bug #164576 +++ Description of problem: When piranha is used with a public + private NIC, any loss of a network path on the master director constitutes a service outage. For example, a normal NAT piranha cluster. The left side are NICs on the public network, and the right side is the private network. The primary node is active: +--> rs0 <---> primary <----> | | | +--> rs1 <---> backup <----> | +--> rs2 If we disconnect the public NIC on the primary node, heartbeats are still being received over the public network, and thus, no failover occurs. This causes an outage. +--> rs0 X---X primary <----> | X | +--> rs1 <---> backup <----> | +--> rs2 The same thing happens if we disconnect the private NIC: heartbeats are still being sent over the public interface, so no failover occurs. +--> rs0 <---> primary X----X | | X +--> rs1 <---> backup <----> | +--> rs2 This reduces the availability of the piranha director cluster. Version-Release number of selected component (if applicable): 0.7.10, 0.8.0 How reproducible: 100% Steps to Reproduce: 1. Create a piranha cluster with a backup. Configure the IPs for the public NICs and private NICs. 2. Start piranha on both nodes. 3. Unplug either the public or private NIC on the master server. Actual results: No failover. Any virtual services will malfunction. Expected results: Failover. Virtual services should be made available. Additional info:
Created attachment 117243 [details] Implementation for 0.8.0 (RHCS4)
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. http://rhn.redhat.com/errata/RHBA-2005-746.html