Project

General

Profile

Bug #9468

Removing the last limiter does not sync to secondary via XMLRPC

Added by Jim Pingle over 1 year ago. Updated 8 months ago.

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

100%

Estimated time:
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.

Associated revisions

Revision c9a96f16 (diff)
Added by Viktor Gurov 9 months ago

XMLRPC: fix last shaper/limiter removing. Issue #9468-9469

Revision de40fb33 (diff)
Added by Viktor Gurov 9 months ago

XMLRPC: fix last shaper/limiter removing. Issue #9468-9469

(cherry picked from commit c9a96f16a4cb582884c8a09d42dd1a61c206b97d)

History

#1 Updated by Jim Pingle about 1 year ago

  • Category changed from Traffic Shaper (ALTQ) to XMLRPC

#2 Updated by Jim Pingle 9 months ago

  • Status changed from New to Pull Request Review

#3 Updated by Renato Botelho 9 months ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Renato Botelho
  • Target version changed from 2.5.0 to 2.4.5
  • % Done changed from 0 to 100

PR has been merged. Thanks!

#4 Updated by Viktor Gurov 8 months ago

Renato Botelho wrote:

PR has been merged. Thanks!

works as expected on 2.5.0.a.20200122.2323

#5 Updated by Viktor Gurov 8 months ago

  • Status changed from Feedback to Resolved

works as expected on 2.4.5.a.20200123.1100

Also available in: Atom PDF