Project

General

Profile

Actions

Bug #2362

closed

Deleting last/only port forward doesn't remove from secondary

Added by Chris Buechler over 9 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Low
Category:
XMLRPC
Target version:
Start date:
04/08/2012
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

if you delete the last/only port forward from the primary, it doesn't get removed from the secondary on config sync.

Actions #1

Updated by Jim Pingle almost 9 years ago

Does this still happen on 2.1? I thought I fixed all of these not too long ago.

Actions #2

Updated by Chris Buechler almost 9 years ago

  • Target version set to 2.1

Yeah it does as of Friday's snapshot at least.

Actions #3

Updated by Renato Botelho almost 9 years ago

  • Assignee set to Renato Botelho
Actions #4

Updated by Renato Botelho almost 9 years ago

Same happens for last/only filter rule. I'm working on a solution.

Actions #5

Updated by Renato Botelho almost 9 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #6

Updated by Ermal Luçi almost 9 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.

Actions #7

Updated by Renato Botelho almost 9 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.

Actions #8

Updated by Chris Buechler over 8 years ago

  • Status changed from Feedback to Resolved
Actions #9

Updated by Jim Pingle over 2 years ago

  • Category changed from 62 to XMLRPC
Actions

Also available in: Atom PDF