Project

General

Profile

Actions
Copy link

Regression #14316

closed
CM JP

Filter/NAT rules configured with "No XMLRPC Sync" enabled are still synchronized

Regression #14316: Filter/NAT rules configured with "No XMLRPC Sync" enabled are still synchronized

Added by Christian McDonald over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Jim Pingle
Category:
XMLRPC
Target version:
2.7.0
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.05
Release Notes:
Default
Affected Version:
Affected Architecture:

Related issues 1 (0 open — 1 closed)

Precedes Bug #14335: Associated firewall rule for NAT port forward does not inherit ``nosync`` property, gets synchronizedResolvedJim Pingle

Actions

SW Updated by Steve Wheeler over 3 years ago Actions
Copy link
 #1

This applies in both 23.01 and 23.05.

JP Updated by Jim Pingle over 3 years ago Actions
Copy link
 #2

  • Assignee set to Jim Pingle

JP Updated by Jim Pingle over 3 years ago Actions
Copy link
 #3

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Fixed in commit:0b612e5498164239ce431e0d61185c8af0627813

The syntax for array_path_enabled() was missing the path parameter so the test was always failing.

JP Updated by Jim Pingle over 3 years ago Actions
Copy link
 #4

  • Subject changed from Filter rules being synced when ```No XMLRPC Sync``` enabled to Filter/NAT rules configured with "No XMLRPC Sync" enabled are still synchronized

Updating subject for release notes.

JP Updated by Jim Pingle over 3 years ago Actions
Copy link
 #5

  • Status changed from Feedback to Resolved

This is working as expected now. Rules marked nosync are no longer being synchronized.

JP Updated by Jim Pingle over 3 years ago Actions
Copy link
 #6

  • Precedes Bug #14335: Associated firewall rule for NAT port forward does not inherit ``nosync`` property, gets synchronized added
Actions
Copy link

Also available in: Atom