Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Not allowed to put at U0 #14401

Closed
Riprock opened this issue Dec 1, 2023 · 1 comment · Fixed by #14439
Closed

Not allowed to put at U0 #14401

Riprock opened this issue Dec 1, 2023 · 1 comment · Fixed by #14439
Assignees
@arthanson
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@Riprock
Copy link

Riprock commented Dec 1, 2023

NetBox version

v3.6.5

Python version

3.11

Steps to Reproduce

image
image
image

This is all preformed in the UI

  1. Create New Rack
  2. Create new Device
  3. Attempt to assign to to U0 To have device be at the bottom of the rack

Expected Behavior

What I expected is it to place the Device in U0-U3 Not to have a 1U gap as shown in pictures above

Observed Behavior

Error was provided in the interface saying I cant put a device at U0 because it has to be 1 or greater
@Riprock Riprock added the type: bug A confirmed report of unexpected behavior in the application label Dec 1, 2023
@Riprock Riprock changed the title Not allowed to put at Not allowed to put at U0 Dec 1, 2023
@jeremystretch
Copy link
Member

0 should not be a permitted value for Rack.starting_unit. The bug is not in the placement of the device, but rather in the failure to validate the minimum value for this field.

@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Dec 1, 2023
@arthanson arthanson removed the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Dec 4, 2023
@arthanson arthanson self-assigned this Dec 4, 2023
@arthanson arthanson mentioned this issue Dec 4, 2023
Closed
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Dec 5, 2023
@arthanson arthanson mentioned this issue Dec 5, 2023
Merged
jeremystretch added a commit that referenced this issue Dec 7, 2023
@jeremystretch
Changelog for #14249, #14390, #14392, #14397, #14401, #14432, #14448
2ef023a
@jeremystretch jeremystretch mentioned this issue Dec 15, 2023
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@arthanson arthanson

Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

14401 validate rack startion position > 0 netbox-community/netbox
3 participants
@arthanson @Riprock @jeremystretch