Project

General

Profile

Actions

Bug #9468

closed

Removing the last limiter does not sync to secondary via XMLRPC

Added by Jim Pingle about 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Category:
XMLRPC
Target version:
Start date:
04/10/2019
Due date:
% Done:

100%

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

Description

With an HA cluster synchronizing settings via XMLRPC, when the last limiter is deleted that change is not reflected on the secondary. The last limiter remains in the configuration on the secondary.

We've hit issues like this in the past in other areas, where the sync only happens when the section is not empty, so that last change gets skipped.

Actions

Also available in: Atom PDF