Actions
Bug #4192
closed
check_reload_status aggregation of CARP events causes issues
Start date:
01/08/2015
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2
Affected Architecture:
Description
This is confirmed fixed on the most recent snapshot, but adding a ticket for tracking purposes.
check_reload_status was aggregating CARP events, leading to it only running rc.carpmaster/backup on two CARP IPs. That could lead to circumstances such as OpenVPN clients bound to a CARP IP not stopping when the system goes to backup status.
After today's changes, rc.carpmaster/backup runs once for each CARP IP, which fixes the issue.
No data to display
Actions