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

Descending units fail to support half-height devices #7182

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

Originally created by @jbakklund on GitHub (Oct 31, 2022).

NetBox version

v3.3.6

Python version

3.9

Steps to Reproduce

  1. Create a rack with descending units, where the units are numbered top-to-bottom.
  2. Add a device consuming the upper half of a rack position.
  3. Try to add a half-height device in the bottom half of the same position.

Add 0 5U device in position U2

Expected Behavior

The half-height device should be allowed to consume the available rackspace between 1.5 and 2.0 in the same way as for a normal rack where units are numbered in ascending order as illustrated below, where a half-height device were allowed to consume rackspace between 41 and 41.5

Added 0 5U device in position U41

Observed Behavior

Observed behavior

Originally created by @jbakklund on GitHub (Oct 31, 2022). ### NetBox version v3.3.6 ### Python version 3.9 ### Steps to Reproduce 1. Create a rack with descending units, where the units are numbered top-to-bottom. 2. Add a device consuming the upper half of a rack position. 3. Try to add a half-height device in the bottom half of the same position. ![Add 0 5U device in position U2](https://user-images.githubusercontent.com/33431806/198998638-53997e79-cee1-4a76-81de-996ead137b29.png) ### Expected Behavior The half-height device should be allowed to consume the available rackspace between 1.5 and 2.0 in the same way as for a normal rack where units are numbered in ascending order as illustrated below, where a half-height device were allowed to consume rackspace between 41 and 41.5 ![Added 0 5U device in position U41](https://user-images.githubusercontent.com/33431806/198998666-af5d6ad7-f75b-4130-8eb0-fbd92f9dc5a8.png) ### Observed Behavior ![Observed behavior](https://user-images.githubusercontent.com/33431806/198986955-fb6a82df-f443-4460-bda5-d77ec00a9f87.png)
adam closed this issue 2025-12-29 20:20:14 +01:00
adam commented 2025-12-29 20:20:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 1, 2022):

As the error message indicates, the U2 position is occupied by the 1.5U device. You need to assign the second device (which is 0.5U high) to the U2.5 position:

Screenshot 2022-11-01 at 15-32-30 Rack R1 NetBox

@jeremystretch commented on GitHub (Nov 1, 2022): As the error message indicates, the U2 position is occupied by the 1.5U device. You need to assign the second device (which is 0.5U high) to the U2.5 position: ![Screenshot 2022-11-01 at 15-32-30 Rack R1 NetBox](https://user-images.githubusercontent.com/13487278/199322285-755d8fb0-577f-4532-857e-cbb4e0a33ab3.png)
adam commented 2025-12-29 20:20:15 +01:00
Author
Owner
Copy Link

@jbakklund commented on GitHub (Nov 3, 2022):

Ah, sorry! My brain didn’t handle the wraparound to consider that the anchor point at the lowest number is now actually at the uppermost edge of the new device.

I should rather file a new feature request then; suggesting to modify the ‘add device’ link in the rack elevation diagram to use the next available position within the unit, instead of integers – to something like: https://netbox.marlink.com/dcim/devices/add/?site=1&location=35&rack=90&face=front&position=2.5

Best regards,
Jostein Bakklund

From: Jeremy Stretch
Sent: tirsdag 1. november 2022 20:33
To: netbox-community/netbox
Cc: Jostein Bakklund; Author
Subject: Re: [netbox-community/netbox] Descending units fail to supporthalf-height devices (Issue #10795)

As the error message indicates, the U2 position is occupied by the 1.5U device. You need to assign the second device (which is 0.5U high) to the U2.5 position:

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@jbakklund commented on GitHub (Nov 3, 2022): Ah, sorry! My brain didn’t handle the wraparound to consider that the anchor point at the lowest number is now actually at the uppermost edge of the new device. I should rather file a new feature request then; suggesting to modify the ‘add device’ link in the rack elevation diagram to use the next available position within the unit, instead of integers – to something like: https://netbox.marlink.com/dcim/devices/add/?site=1&location=35&rack=90&face=front&position=2.5 Best regards, Jostein Bakklund From: Jeremy Stretch Sent: tirsdag 1. november 2022 20:33 To: netbox-community/netbox Cc: Jostein Bakklund; Author Subject: Re: [netbox-community/netbox] Descending units fail to supporthalf-height devices (Issue #10795) As the error message indicates, the U2 position is occupied by the 1.5U device. You need to assign the second device (which is 0.5U high) to the U2.5 position: — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>
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
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#7182
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?