Project

General

Profile

Actions

Regression #14327

closed

Gateway popup in firewall rule list does not indicate current gateway status

Added by Danilo Zrenjanin over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Gateways
Target version:
Start date:
Due date:
% Done:

100%

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

Description

Hovering a Gateway Group, defined in a Firewall Rule, shows the gateways participating in the group. However, the gateways are not listed by the priority level, which can easily trick you into thinking that the first gateway in the list is currently used for forwarding the traffic.



Files

clipboard-202304291934-uk7l1.png (574 KB) clipboard-202304291934-uk7l1.png Danilo Zrenjanin, 04/29/2023 05:34 PM
clipboard-202304291935-eahuh.png (76.4 KB) clipboard-202304291935-eahuh.png Danilo Zrenjanin, 04/29/2023 05:35 PM
Actions #1

Updated by Jim Pingle over 1 year ago

  • Tracker changed from Feature to Regression
  • Subject changed from Order gateways by the priority level when hovering over Gateway defined in a policy based rule to Gateway popup in firewall rule list does not indicate current gateway status
  • Status changed from New to In Progress
  • Assignee set to Jim Pingle
  • Target version set to 2.7.0
  • Plus Target Version set to 23.05

This is actually a bug, not a missing feature. The gateway popup should be showing the gateway group status with the active tier(s) marked in green. It's showing everything with a generic status indicating that it isn't reading the status data properly.

This has apparently been broken since 22.05 at least, it was working in the past.

Actions #2

Updated by Jim Pingle over 1 year ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100

Fixed in d357172cfcbc5def693a8948ba95b068bd5f4ab2 it will be in the next 23.05 snapshot.

The fix also applies cleanly against 23.01. You can install the System Patches package and then create an entry for d357172cfcbc5def693a8948ba95b068bd5f4ab2 to apply the fix.

Actions #3

Updated by Danilo Zrenjanin over 1 year ago

  • Status changed from Feedback to Resolved

The patch fixes it. Thanks!

I am marking this one resolved.

Actions

Also available in: Atom PDF