Project

General

Profile

Actions
Copy link

Bug #2362

closed

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

Added by Chris Buechler about 12 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Renato Botelho
Category:
XMLRPC
Target version:
2.1
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
Copy link
 #1

Updated by Jim Pingle about 11 years ago

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

Actions
Copy link
 #2

Updated by Chris Buechler about 11 years ago

  • Target version set to 2.1

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

Actions
Copy link
 #3

Updated by Renato Botelho about 11 years ago

  • Assignee set to Renato Botelho
Actions
Copy link
 #4

Updated by Renato Botelho about 11 years ago

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

Actions
Copy link
 #5

Updated by Renato Botelho about 11 years ago

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

Updated by Ermal Luçi about 11 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
Copy link
 #7

Updated by Renato Botelho about 11 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
Copy link
 #8

Updated by Chris Buechler about 11 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #9

Updated by Jim Pingle over 4 years ago

  • Category changed from 62 to XMLRPC
Actions
Copy link

Also available in: Atom PDF