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

Available rear U's position is locked if there is a non full-depth device mounted to front position #5436

New Issue
Closed
opened 2025-12-29 19:27:55 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:27:55 +01:00
Owner
Copy Link

Originally created by @mmfreitas on GitHub (Sep 28, 2021).

NetBox version

v3.0.3

Python version

3.7

Steps to Reproduce

  1. Add a non full-depth device and set it to the front U's position of a rack
  2. Try to add another non full-depth device to the rear of the same rack in the same U's position

Expected Behavior

Expected the number in positions field to show available rear U's positions as it is possible to add a device in this position through the "add device" on the elevations page.

Observed Behavior

When creating a non full-depth device and assigning it to the front U of a rack, the rear positions of this rack are locked when trying to add another non full-depth device.

Originally created by @mmfreitas on GitHub (Sep 28, 2021). ### NetBox version v3.0.3 ### Python version 3.7 ### Steps to Reproduce 1. Add a non full-depth device and set it to the front U's position of a rack 2. Try to add another non full-depth device to the rear of the same rack in the same U's position ### Expected Behavior Expected the number in positions field to show available rear U's positions as it is possible to add a device in this position through the "add device" on the elevations page. ### Observed Behavior When creating a non full-depth device and assigning it to the front U of a rack, the rear positions of this rack are locked when trying to add another non full-depth device.
adam added the type: bugstatus: duplicate labels 2025-12-29 19:27:55 +01:00
adam closed this issue 2025-12-29 19:27:55 +01:00
adam commented 2025-12-29 19:27:55 +01:00
Author
Owner
Copy Link

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

Duplicate of #7374

@DanSheps commented on GitHub (Sep 28, 2021): Duplicate of #7374
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: duplicate 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#5436
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?