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

Device rack position grayed out when non-full depth device are on same RU #5429

New Issue
Closed
opened 2025-12-29 19:27:51 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:27:51 +01:00
Owner
Copy Link

Originally created by @netgab on GitHub (Sep 27, 2021).

Originally assigned to: @DanSheps on GitHub.

NetBox version

v3.0.3 (community docker image)

Python version

3.9

Steps to Reproduce

  1. Create a standard 19" rack (e.g. 4 post)
  2. Create a device type which is not a full-depth device
  3. Create two device instances of the device type (deviceA and deviceB)
  4. Place deviceA to the rack front RU40
  5. Place deviceB to the rack rear RU40

Note: I wanted to reproduce it in the demo instance, but the outlined credentials admin/admin are not valid.

Expected Behavior

Both devices (deviceA and deviceB) should be placed successfully in the rack.
deviceA => RU40 front
deviceB => RU40 rear

Observed Behavior

deviceB cannot be placed to rack rear RU40. In the edit device dialog, when the rack and the rack face "rear" is selected, RU40 is not selectable (greyed out).
However in the rack view, RU40 in the rear is still free and a new device may be created there.
Using nbshell, deviceB can be assigned to the rack rear in the desired position.

Also check out the screenshots in the Google groups: https://groups.google.com/g/netbox-discuss/c/zgBhnTUiaHs/m/tMsrXVbrAwAJ

Originally created by @netgab on GitHub (Sep 27, 2021). Originally assigned to: @DanSheps on GitHub. ### NetBox version v3.0.3 (community docker image) ### Python version 3.9 ### Steps to Reproduce 1. Create a standard 19" rack (e.g. 4 post) 2. Create a device type which is not a full-depth device 2. Create two device instances of the device type (deviceA and deviceB) 3. Place deviceA to the rack front RU40 4. Place deviceB to the rack rear RU40 Note: I wanted to reproduce it in the demo instance, but the outlined credentials admin/admin are not valid. ### Expected Behavior Both devices (deviceA and deviceB) should be placed successfully in the rack. deviceA => RU40 front deviceB => RU40 rear ### Observed Behavior deviceB cannot be placed to rack rear RU40. In the edit device dialog, when the rack and the rack face "rear" is selected, RU40 is not selectable (greyed out). However in the rack view, RU40 in the rear is still free and a new device may be created there. Using nbshell, deviceB can be assigned to the rack rear in the desired position. Also check out the screenshots in the Google groups: https://groups.google.com/g/netbox-discuss/c/zgBhnTUiaHs/m/tMsrXVbrAwAJ
adam added the type: bugstatus: accepted labels 2025-12-29 19:27:51 +01:00
adam closed this issue 2025-12-29 19:27:51 +01:00
adam commented 2025-12-29 19:27:51 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Sep 28, 2021):

Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v3.0.3. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.

@DanSheps commented on GitHub (Sep 28, 2021): Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v3.0.3. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.
adam commented 2025-12-29 19:27:52 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Sep 28, 2021):

Scratch that.

You can add it from the rack view if you click on the rack u, but it is indeed grayed out in the selection box.

@DanSheps commented on GitHub (Sep 28, 2021): Scratch that. You can add it from the rack view if you click on the rack u, but it is indeed grayed out in the selection box.
adam commented 2025-12-29 19:27:52 +01:00
Author
Owner
Copy Link

@netgab commented on GitHub (Sep 28, 2021):

Wow, that was fast! Thank you for fixing this @DanSheps !

@netgab commented on GitHub (Sep 28, 2021): Wow, that was fast! Thank you for fixing this @DanSheps !
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#5429
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?