Regression #11568
closedAlias name change is not reflected in firewall rules
0%
Description
To reproduce the issue:
- Create an alias ( ip or port )
- Make a firewall rule containing the alias ( source or destination )
- Apply the rule and verify it is displayed as an alias in the rule table (hover over alias name)
- Edit the alias and rename it
- Go back to the firewall rules page. Verify that the new alias name appears and that the correct alias targets are displayed when hovering over the name.
JP Updated by Jim Pingle over 5 years ago
- Subject changed from Alias rename not updating firewall rules ( causing Unresolvable destination alias error ) to Alias name change is not reflected in firewall rules
- Status changed from New to Resolved
- Assignee set to Anonymous
- Target version set to CE-Next
- Affected Version set to 2.5.0
Already fixed in NG 5685 and commit:6ecf793e0f4a5c3922c5c00a087a1adea104e50a (master) commit:585e7567d0e308ce440ff1b0651976c97fe58115 (RELENG_2_5_0).
Closing this since the other entry is on our internal Redmine
JP Updated by Jim Pingle over 5 years ago
- Tracker changed from Bug to Regression
JP Updated by Jim Pingle over 5 years ago
- Target version changed from CE-Next to 2.5.1
JP Updated by Jim Pingle over 5 years ago
- Status changed from Resolved to Feedback
Needs re-tested on snapshots.
Updated by Anonymous over 5 years ago
- Description updated (diff)
AZ Updated by Alhusein Zawi over 5 years ago
- Status changed from Feedback to Resolved
new alias name appears after changing the name.
targets are displayed
tested on IP & IP aliases.
2.5.1-RC (amd64)
built on Thu Mar 11 09:11:02 EST 2021