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

wrong order of module bays #10222

New Issue
Closed
opened 2025-12-29 21:28:33 +01:00 by adam · 5 comments
adam commented 2025-12-29 21:28:33 +01:00
Owner
Copy Link

Originally created by @Jarod2801 on GitHub (Sep 11, 2024).

Originally assigned to: @arthanson on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.0.9

Python Version

3.10

Steps to Reproduce

  1. create a device type
  2. create modile bays in this device type
    a.) Name: "Slot [0-16]"
    b.) Label: "Slot [0-16]"
    c.) Position: "[0-16]"
  3. create a device of that type

In the created device, module bays are shown but in wrong order.
Expected orden would be
0-1-2-3-4-5-6-7-8-9-10-11-12-13-14-15-16
But the order is
0-1-10-11-12-13-14-15-16-2-3-4-5-6-7-8-9

This is really annoying when having a 16 Slot-Shelf in front of you and NetBox is displaying the Slots in a wrong order.

Expected Behavior

order
0-1-2-3-4-5-6-7-8-9-10-11-12-13-14-15-16

Observed Behavior

order
0-1-10-11-12-13-14-15-16-2-3-4-5-6-7-8-9

Originally created by @Jarod2801 on GitHub (Sep 11, 2024). Originally assigned to: @arthanson on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.0.9 ### Python Version 3.10 ### Steps to Reproduce 1. create a device type 2. create modile bays in this device type a.) Name: "Slot [0-16]" b.) Label: "Slot [0-16]" c.) Position: "[0-16]" 3. create a device of that type In the created device, module bays are shown but in wrong order. Expected orden would be 0-1-2-3-4-5-6-7-8-9-10-11-12-13-14-15-16 But the order is 0-1-10-11-12-13-14-15-16-2-3-4-5-6-7-8-9 This is really annoying when having a 16 Slot-Shelf in front of you and NetBox is displaying the Slots in a wrong order. ### Expected Behavior order 0-1-2-3-4-5-6-7-8-9-10-11-12-13-14-15-16 ### Observed Behavior order 0-1-10-11-12-13-14-15-16-2-3-4-5-6-7-8-9
adam added the type: bugstatus: revisions needed labels 2025-12-29 21:28:33 +01:00
adam closed this issue 2025-12-29 21:28:34 +01:00
adam commented 2025-12-29 21:28:34 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Sep 11, 2024):

@Jarod2801 can you please check this on NetBox v4.1 as I think it is either fixed or I can't reproduce. I just created a new device type and added the module bays as per your repro and the ordering was correct:
APC tdev1 | NetBox 2024-09-11 07-42-10

@arthanson commented on GitHub (Sep 11, 2024): @Jarod2801 can you please check this on NetBox v4.1 as I think it is either fixed or I can't reproduce. I just created a new device type and added the module bays as per your repro and the ordering was correct: ![APC tdev1 | NetBox 2024-09-11 07-42-10](https://github.com/user-attachments/assets/044e6d25-afe5-4a7c-9e91-fe2c424681b5)
adam commented 2025-12-29 21:28:35 +01:00
Author
Owner
Copy Link

@Jarod2801 commented on GitHub (Sep 11, 2024):

Have you created a device as of that type?

I am offline ATM but I think it happened when creating the device, not the module bays in the device type

@Jarod2801 commented on GitHub (Sep 11, 2024): Have you created a device as of that type? I am offline ATM but I think it happened when creating the device, not the module bays in the device type
adam commented 2025-12-29 21:28:35 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Sep 11, 2024):

@Jarod2801 yes, it looks fine:
aaa | NetBox 2024-09-11 07-56-13

@arthanson commented on GitHub (Sep 11, 2024): @Jarod2801 yes, it looks fine: ![aaa | NetBox 2024-09-11 07-56-13](https://github.com/user-attachments/assets/6856bb39-9156-4f09-8039-381e26222ff7)
adam commented 2025-12-29 21:28:35 +01:00
Author
Owner
Copy Link

@Jarod2801 commented on GitHub (Sep 11, 2024):

Hm.

I will have to recheck.

@Jarod2801 commented on GitHub (Sep 11, 2024): Hm. I will have to recheck.
adam commented 2025-12-29 21:28:36 +01:00
Author
Owner
Copy Link

@Jarod2801 commented on GitHub (Sep 12, 2024):

I tried to reproduce but it looks like I made sth. wrong yesteday.
Order looks fine.

So I also can`t reproduce

@Jarod2801 commented on GitHub (Sep 12, 2024): I tried to reproduce but it looks like I made sth. wrong yesteday. Order looks fine. So I also can`t reproduce
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#10222
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?