Project

General

Profile

Actions
Copy link

Bug #7663

closed

Persistent CARP Maintenance Mode doesn't work right in upgrade from 2.3.3-RELEASE-p1 to 2.3.4

Added by Whit Blauvelt almost 7 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
CARP
Target version:
-
Start date:
06/27/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

Upgrading the OS to 2.3.4 from 2.3.3-RELEASE-p1 with Persistent CARP Maintenance Mode selected, the OS rebooted with that still selected, but it had taken over the IP groups that in normal operation are handled by the twin, that had not been upgraded yet and which kept those IPs active through this. So not only did it not prevent IPs from being taken over, but it resulted in the wrong set of the IPs being taken over.

Actions
Copy link
 #1

Updated by Jim Pingle over 4 years ago

  • Category set to CARP
  • Status changed from New to Closed

Old report and no recent recurrences. Lots of things in this area have changed, so most likely it's either fixed no longer relevant.

Actions
Copy link

Also available in: Atom PDF