Project

General

Profile

Bug #8806

HA sync : Starting captiveportal doesn't fire ipfw rules on slave, even if HA is enabled.

Added by A FL 7 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Category:
Captive Portal
Target version:
Start date:
08/19/2018
Due date:
% Done:

100%

Estimated time:
Affected Version:
All
Affected Architecture:
All

Description

When a CP zone is enabled, slave does not start the captive portal (despite "enabled" setting appear checked on the slave):
One workaround to this is to manually start captiveportal on the slave by clicking "submit" on the salve cp settings, or by rebooting the slave.

I think it would be better to automatically start the slave if captiveportal sync is ensabled in System-> High Avaliablity settings

Associated revisions

Revision 7cab6335 (diff)
Added by Renato Botelho 7 months ago

Fix #8806: Configure captive portal on secondary identical as master HA node

History

#1 Updated by Jim Pingle 7 months ago

  • Target version set to 2.4.4

I wonder if this might be the same root cause as #8721

An XMLRPC sync used to trigger filter_configure via XMLRPC which handled refreshing a number of things on the secondary after a sync. It doesn't now, which may be the cause of these issues.

#2 Updated by Steve Beaver 7 months ago

  • Assignee set to Renato Botelho

#3 Updated by Steve Beaver 7 months ago

  • Priority changed from Normal to Normal-package

#4 Updated by Steve Beaver 7 months ago

  • Priority changed from Normal-package to Normal

#5 Updated by Renato Botelho 7 months ago

  • Status changed from New to In Progress

#6 Updated by Renato Botelho 7 months ago

  • Status changed from In Progress to Feedback

#7 Updated by Renato Botelho 7 months ago

  • % Done changed from 0 to 100

#8 Updated by A FL 7 months ago

Working correctly on the last snapshot

This issue can be marked as resolved.

#9 Updated by Steve Beaver 7 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF