Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Child prefixes change order in the aggregate's list when Hide available is selected #4455

Closed
markkuleinio opened this issue Apr 6, 2020 · 2 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@markkuleinio
Copy link
Contributor

Environment

  • Python version: 3.7.3
  • NetBox version: 2.7.11

Steps to Reproduce

  1. Create RIR for example "RFC1918"
  2. Create Aggregate 10.0.0.0/8 with RIR RFC1918
  3. Create VRF for example "Test VRF"
  4. Create prefix 10.1.0.0/16 in "Test VRF"
  5. Create prefix 10.2.0.0/16 with no VRF (= Global)
  6. Go to Aggregates - 10.0.0.0/8
  7. See that the list shows prefixes in IP-ordered: 10.1.0.0/16, 10.2.0.0/16 (as well as available prefixes)
  8. Click Hide available

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)

@markkuleinio markkuleinio changed the title Prefixes change order in Aggregates list when Hide available is selected Child prefixes change order in the aggregate's list when Hide available is selected Apr 6, 2020
@lampwins lampwins added status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application labels Apr 20, 2020
@DanSheps
Copy link
Member

I think this might be related to the same issue with IP Prefix hierarchy getting broken, FYI.

@jeremystretch
Copy link
Member

Tagging as possibly related to #4617

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

4 participants