Child prefixes change order in the aggregate's list when Hide available is selected #4455
Labels
status: accepted
This issue has been accepted for implementation
type: bug
A confirmed report of unexpected behavior in the application
Environment
Steps to Reproduce
Expected Behavior
The active prefixes would still show in the same order: 10.1.0.0/16, 10.2.0.0/16, just the available prefixes hidden
Observed Behavior
The prefixes are shown in reverse order 10.2.0.0/16, 10.1.0.0/16 (i.e. Global prefix is shown first, VRF second)
The text was updated successfully, but these errors were encountered: