Project

General

Profile

Bug #3807

Unable to edit existing Virtual IPs

Added by Trond Vindenes almost 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
High
Category:
Virtual IPs
Target version:
Start date:
08/16/2014
Due date:
% Done:

100%

Affected Version:
2.2
Affected Architecture:

Description

Using "2.2-ALPHA (amd64) built on Fri Aug 15 14:31:24 CDT 2014".

Simple "High Avail. Sync" setup with two CARP IPs, one for WAN and another for LAN. I'm unable to change already created CARP IPs. Even just changing the description of a CARP IP, I get the following validation error:

The following input errors were detected:

This IP address is being used by another interface or VIP.

From the error message, could it be that it's trying to create a new CARP IP, instead of changing the existing one?

Associated revisions

Revision d5971693
Added by Renato Botelho almost 4 years ago

Fix #3807:

  • When changing a pre existing VIP, use previous configured interface
    for checking, this fixes the issue that happens when you try to change
    a VIP to a new interface.
  • Use the right interface name, only carp uses _vipN suffix

Revision 4665dbdd
Added by Renato Botelho over 3 years ago

Make proper check if IP address is configured on another interfaces and ignore current one. It fixes #3807

History

#1 Updated by Trond Vindenes almost 4 years ago

When I change the actual IP address on the CARP IP, it works. Does not create a new one, it alters the existing.

#2 Updated by Chris Buechler almost 4 years ago

  • Subject changed from Unable to change an existing CARP IP to Unable to edit existing Virtual IPs
  • Category set to Virtual IPs
  • Priority changed from Normal to High
  • Target version set to 2.2

In addition to the problem as described here, it's also impossible to change the interface on a VIP on 2.2 because of this bug.

#3 Updated by Renato Botelho almost 4 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#4 Updated by Jim Thompson almost 4 years ago

  • Assignee set to Renato Botelho

#5 Updated by Trond Vindenes almost 4 years ago

Using "2.2-ALPHA (amd64) built on Sat Sep 13 00:05:21 CDT 2014" nanobsd, and I'm still not able to edit existing virtual IP. This is on a active/backup CARP setup with multiple VLANs, that was recently upgraded from 2.1.5.

#6 Updated by Chris Buechler over 3 years ago

  • Status changed from Feedback to New

original issue still exists

#7 Updated by Renato Botelho over 3 years ago

  • Status changed from New to Feedback

#8 Updated by Chris Buechler over 3 years ago

  • Status changed from Feedback to Resolved

fixed

Also available in: Atom PDF