Project

General

Profile

Actions

Bug #3909

closed

carp_status.php shows disabled after initial config when it really isn't

Added by Chris Buechler about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
High Availability
Target version:
Start date:
10/02/2014
Due date:
% Done:

100%

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

Description

To replicate:

Take a clean default config, and add a CARP IP. Apply changes. Go to Status>CARP. It shows disabled. The CARP VIPs are actually enabled and configured in the underlying system just fine and work fine.

Enabling CARP in that manner has never been necessary, and still isn't necessary for it to work, just for it to show correct status.

This isn't applicable to the secondary system, its status shows "backup" as it should.

Actions

Also available in: Atom PDF