Actions
Bug #9469
closed
JP
RB
Removing the last ATLQ traffic shaper queue does not sync to secondary via XMLRPC
Bug #9469:
Removing the last ATLQ traffic shaper queue 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 ATLQ traffic shaper queue is deleted that change is not reflected on the secondary. The last queue remains in the configuration on the secondary. If the user clicks the button to remove the traffic shaper settings, then all settings remain 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.
JP Updated by Jim Pingle about 7 years ago
- Category changed from Traffic Shaper (ALTQ) to XMLRPC
VG Updated by Viktor Gurov over 6 years ago
JP Updated by Jim Pingle over 6 years ago
- Status changed from New to Pull Request Review
RB Updated by Renato Botelho over 6 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!
VG Updated by Viktor Gurov over 6 years ago
Renato Botelho wrote:
PR has been merged. Thanks!
works as expected on 2.5.0.a.20200122.2323
VG Updated by Viktor Gurov over 6 years ago
- Status changed from Feedback to Resolved
works as expected on 2.4.5.a.20200123.1100
Actions