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

DCIM Locations ordering issue #9026

New Issue
Closed
opened 2025-12-29 20:44:22 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:44:22 +01:00
Owner
Copy Link

Originally created by @duckw on GitHub (Jan 3, 2024).

Deployment Type

Self-hosted

NetBox Version

v3.7.0

Python Version

3.9

Steps to Reproduce

I have not been able to reproduce this in another instance and need assistance in being able to provide sufficient information so that this can be remediated. This has been observed since v3.4 at least.

  1. Create locations with the structure as shown below in the expected behaviour.
  2. Go to the /dcim/locations/ page and confirm ordering is not correct.
  3. Go into the incorrectly placed location and confirm the correct parent.

Expected Behavior

Locations created with this hierarchy.

ABC-B1
* ABC-B1-L1
* * ABC-B1-L1-SVR
* * ABC-B1-L1A
* * ABC-B1-L1B
* * ABC-B1-L1C
* ABC-B1-L2
* * ABC-B1-L2A
* * ABC-B1-L2B
* ABC-B1-L3
* * ABC-B1-L3A
* * ABC-B1-L3B
* ABC-B1-L4
* * ABC-B1-L4A
* * ABC-B1-L4B
* ABC-B1-L5
* * ABC-B1-L5A
* * ABC-B1-L5B
* ABC-B1-L6
* * ABC-B1-L6A
* * ABC-B1-L6B
* ABC-B1-L7
* * ABC-B1-L7A
* * ABC-B1-L7B

Observed Behavior

Locations are shown in /dcim/locations/ in this order: (note: ABC-B1-L2B, ABC-B1-L4B, ABC-B1-L7A are incorrect).

ABC-B1
* ABC-B1-L1
* * ABC-B1-L1-SVR
* * ABC-B1-L1A
* * ABC-B1-L1B
* * ABC-B1-L1C
* ABC-B1-L2
* * ABC-B1-L2A
* ABC-B1-L3
* * ABC-B1-L2B
* * ABC-B1-L3A
* * ABC-B1-L3B
* ABC-B1-L4
* * ABC-B1-L4A
* ABC-B1-L5
* * ABC-B1-L4B
* * ABC-B1-L5A
* * ABC-B1-L5B
* ABC-B1-L6
* * ABC-B1-L6A
* * ABC-B1-L6B
* * ABC-B1-L7A
* ABC-B1-L7
* * ABC-B1-L7B
Originally created by @duckw on GitHub (Jan 3, 2024). ### Deployment Type Self-hosted ### NetBox Version v3.7.0 ### Python Version 3.9 ### Steps to Reproduce I have not been able to reproduce this in another instance and need assistance in being able to provide sufficient information so that this can be remediated. This has been observed since v3.4 at least. 1. Create locations with the structure as shown below in the expected behaviour. 2. Go to the /dcim/locations/ page and confirm ordering is not correct. 3. Go into the incorrectly placed location and confirm the correct parent. ### Expected Behavior Locations created with this hierarchy. ``` ABC-B1 * ABC-B1-L1 * * ABC-B1-L1-SVR * * ABC-B1-L1A * * ABC-B1-L1B * * ABC-B1-L1C * ABC-B1-L2 * * ABC-B1-L2A * * ABC-B1-L2B * ABC-B1-L3 * * ABC-B1-L3A * * ABC-B1-L3B * ABC-B1-L4 * * ABC-B1-L4A * * ABC-B1-L4B * ABC-B1-L5 * * ABC-B1-L5A * * ABC-B1-L5B * ABC-B1-L6 * * ABC-B1-L6A * * ABC-B1-L6B * ABC-B1-L7 * * ABC-B1-L7A * * ABC-B1-L7B ``` ### Observed Behavior Locations are shown in /dcim/locations/ in this order: (note: ABC-B1-L2B, ABC-B1-L4B, ABC-B1-L7A are incorrect). ``` ABC-B1 * ABC-B1-L1 * * ABC-B1-L1-SVR * * ABC-B1-L1A * * ABC-B1-L1B * * ABC-B1-L1C * ABC-B1-L2 * * ABC-B1-L2A * ABC-B1-L3 * * ABC-B1-L2B * * ABC-B1-L3A * * ABC-B1-L3B * ABC-B1-L4 * * ABC-B1-L4A * ABC-B1-L5 * * ABC-B1-L4B * * ABC-B1-L5A * * ABC-B1-L5B * ABC-B1-L6 * * ABC-B1-L6A * * ABC-B1-L6B * * ABC-B1-L7A * ABC-B1-L7 * * ABC-B1-L7B ```
adam added the type: bugstatus: revisions needed labels 2025-12-29 20:44:22 +01:00
adam closed this issue 2025-12-29 20:44:22 +01:00
adam commented 2025-12-29 20:44:23 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 3, 2024):

I have not been able to reproduce this in another instance and need assistance in being able to provide sufficient information so that this can be remediated.

I'm not sure what you're hoping someone can help you with here. If you haven't been able to reproduce it, how would anyone else?

@jeremystretch commented on GitHub (Jan 3, 2024): > I have not been able to reproduce this in another instance and need assistance in being able to provide sufficient information so that this can be remediated. I'm not sure what you're hoping someone can help you with here. If you haven't been able to reproduce it, how would anyone else?
adam commented 2025-12-29 20:44:23 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Jan 3, 2024):

I've seen this happen before when the MPTT structure got messed up and it just required a rebuild to fix it. See #9196 for reference.

@sleepinggenius2 commented on GitHub (Jan 3, 2024): I've seen this happen before when the MPTT structure got messed up and it just required a rebuild to fix it. See #9196 for reference.
adam commented 2025-12-29 20:44:23 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Jan 3, 2024):

No doubt this kind of thing can happen when MPTT goes wrong, but we still need clear and deterministic steps to reproduce the problem. Absent those steps, there's no work to be done, only a problem to be solved.

I'm converting this issue to a discussion so that you can seek help solving this problem in your environment. If in the course of that conversation you come up with repro steps, please do open a new bug issue!

@jeffgdotorg commented on GitHub (Jan 3, 2024): No doubt this kind of thing can happen when MPTT goes wrong, but we still need clear and deterministic steps to reproduce the problem. Absent those steps, there's no work to be done, only a problem to be solved. I'm converting this issue to a discussion so that you can seek help solving this problem in your environment. If in the course of that conversation you come up with repro steps, please do open a new bug issue!
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: revisions needed 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#9026
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?