Actions
Bug #9468
closedRemoving the last limiter does not sync to secondary via XMLRPC
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.
Updated by Jim Pingle about 5 years ago
- Category changed from Traffic Shaper (ALTQ) to XMLRPC
Updated by Jim Pingle almost 5 years ago
- Status changed from New to Pull Request Review
Updated by Renato Botelho almost 5 years 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!
Updated by Viktor Gurov almost 5 years ago
Renato Botelho wrote:
PR has been merged. Thanks!
works as expected on 2.5.0.a.20200122.2323
Updated by Viktor Gurov almost 5 years ago
- Status changed from Feedback to Resolved
works as expected on 2.4.5.a.20200123.1100
Actions