Bug #2362
closed
Deleting last/only port forward doesn't remove from secondary
100%
Description
if you delete the last/only port forward from the primary, it doesn't get removed from the secondary on config sync.
Updated by Jim Pingle almost 12 years ago
Does this still happen on 2.1? I thought I fixed all of these not too long ago.
Updated by Chris Buechler almost 12 years ago
- Target version set to 2.1
Yeah it does as of Friday's snapshot at least.
Updated by Renato Botelho almost 12 years ago
Same happens for last/only filter rule. I'm working on a solution.
Updated by Renato Botelho almost 12 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset a1fb7d61c4be90e6b6fcbc44fd644677cb0761e4.
Updated by Ermal Luçi almost 12 years ago
If those seciton need to be synched no matter what than its better to remove the options completely from the filter sync configuration page to not create the impression this is controllable.
Updated by Renato Botelho almost 12 years ago
I don't believe option should be removed since it is still valid for rules from Master you don't want to sync.
- Rules set to nosync on Master won't be send to Slave.
- All rules on Slave will be overwritten.
Updated by Chris Buechler almost 12 years ago
- Status changed from Feedback to Resolved