Bug #4116
closed
IP Alias VIPs using CARP VIP as their interface are not properly deactivated for temporary CARP disable
100%
Description
When using "Temporarily Disable CARP", IP alias VIPs using a CARP VIP "interface" are still present and the interface flips back to MASTER for the alias VIPs which is unexpected/undesirable. When temporarily disabling CARP mode, the CARP VIP is removed but the aliases using it as an interface are left behind, which may be part of the issue.
When using maintenance mode, the advskew is raised which avoids that specific problem.
Easy to reproduce by adding a CARP VIP to a cluster, then adding an IP Alias VIP using that CARP VIP as its interface, and then test manual/temporary failover from Status > CARP.
Updated by Renato Botelho over 9 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset dd0cb9fcf4428d8fdc0e6cd380ea2a5dff4e9114.
Updated by Renato Botelho over 9 years ago
Applied in changeset 936e554bab69b0f6b1eb53cae807e3f2fafa3e73.
Updated by Jim Pingle over 9 years ago
The "temporary" button seems to behave OK in my test setup now but maintenance mode still does not appear to work properly when a VIP is defined. Might be still related to this, or it may be part of #3910. Entering maintenance mode is OK but it will never return to MASTER status for an interface with an IP Alias VIP on a CARP VIP. Other interfaces are OK. Feel free to close this in favor of #3910 if it's a better fit there.
Updated by Chris Buechler over 9 years ago
- Status changed from Feedback to Confirmed
confirmed current status as Jim described. Temporary is fine. Maintenance mode gets stuck at advskew 254 only on interfaces where you have an IP alias with a CARP IP parent.
Updated by Renato Botelho over 9 years ago
- Status changed from Confirmed to Resolved