Removing the last ATLQ traffic shaper queue does not sync to secondary via XMLRPC
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.