Actions
Bug #5705
closed
CARP Vips sometimes not seen as targets after upgrade to 2.3-ALPHA
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
12/28/2015
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
Description
Hi there,
I've noticed that in several places throughout pfsense, my CARP vips aren't being recognized as viable targets in places where I'd expect them to be.
A few examples are the 'Carp monitor' drop-down in haproxy's settings -> general settings page (haproxy_global.php)
in the 'Network Interfaces' and 'Outgoing Network Interfaces' of the general settings of unbound (services_unbound.php)
Deleting the carp interface, and re-creating it within 2.3 causes the interface to re-appear, so I suspect that the configuration isn't being propagated someplace properly on import of a <2.3 config.
Updated by Jim Pingle almost 9 years ago
- Status changed from New to Rejected
Actions