Project

General

Profile

Bug #776

Interface IP not configured when there is an IP alias and interface is reassigned

Added by Erik Fonnesbeck almost 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
07/30/2010
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

If you have an interface that has an IP alias VIP on it and reassign the interface, for a moment the newly assigned interface has the IP addresses it should have, but then the main IP gets deleted by the time the reassignment completes. The IP alias still does get configured, though. Possibly all of the IP addresses are getting removed at some point and only the IP alias is getting added back.

Associated revisions

Revision 89830b60 (diff)
Added by Ermal Luçi almost 9 years ago

Ticket #776. reload even ipalias type of vip when reloading carps and do not destroy cloned interfaces on interface bring down.

History

#1 Updated by Erik Fonnesbeck almost 9 years ago

A workaround for this is to save and apply on the configuration page for each of the reassigned interfaces. The IP alias is still listed first in the ifconfig output, though, which might still cause problems elsewhere if anything depends on that order.

#2 Updated by Ermal Luçi almost 9 years ago

  • Status changed from New to Feedback

#3 Updated by Chris Buechler almost 9 years ago

  • Status changed from Feedback to Resolved

this is fixed (though there is a related issue in another ticket, IP Alias VIPs don't get removed from the previously assigned interface)

Also available in: Atom PDF