starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

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

New Issue
Closed
opened 2025-12-29 18:29:47 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:29:47 +01:00
Owner
Copy Link

Originally created by @markkuleinio on GitHub (Apr 6, 2020).

Originally assigned to: @jeremystretch on GitHub.

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)

Originally created by @markkuleinio on GitHub (Apr 6, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.7.3 * NetBox version: 2.7.11 ### Steps to Reproduce 1. Create RIR for example "RFC1918" 1. Create Aggregate 10.0.0.0/8 with RIR RFC1918 1. Create VRF for example "Test VRF" 1. Create prefix 10.1.0.0/16 in "Test VRF" 1. Create prefix 10.2.0.0/16 with no VRF (= Global) 1. Go to **Aggregates - 10.0.0.0/8** 1. See that the list shows prefixes in IP-ordered: 10.1.0.0/16, 10.2.0.0/16 (as well as available prefixes) 1. Click **Hide available** <!-- What did you expect to happen? --> ### 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 <!-- What happened instead? --> ### 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)
adam added the type: bugstatus: accepted labels 2025-12-29 18:29:47 +01:00
adam closed this issue 2025-12-29 18:29:47 +01:00
adam commented 2025-12-29 18:29:48 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (May 13, 2020):

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

@DanSheps commented on GitHub (May 13, 2020): I think this might be related to the same issue with IP Prefix hierarchy getting broken, FYI.
adam commented 2025-12-29 18:29:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 13, 2020):

Tagging as possibly related to #4617

@jeremystretch commented on GitHub (May 13, 2020): Tagging as possibly related to #4617
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3544
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?