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.

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

Typo in Device model #15111

Closed
grncbg opened this issue Feb 11, 2024 · 0 comments · Fixed by #15112
Closed

Typo in Device model #15111

grncbg opened this issue Feb 11, 2024 · 0 comments · Fixed by #15112
Assignees
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

@grncbg
Copy link
Contributor

grncbg commented Feb 11, 2024

Deployment Type

Self-hosted

NetBox Version

v3.7.2

Python Version

3.8

Steps to Reproduce

error message is defined as "A U0 device type ...", but I think the correct definition is "A 0U device type ...".

# Prevent 0U devices from being assigned to a specific position
if hasattr(self, 'device_type'):
if self.position and self.device_type.u_height == 0:
raise ValidationError({
'position': _(
"A U0 device type ({device_type}) cannot be assigned to a rack position."
).format(device_type=self.device_type)
})

Expected Behavior

A 0U device type ({device_type}) cannot be assigned to a rack position.

Observed Behavior

A U0 device type ({device_type}) cannot be assigned to a rack position.

@grncbg grncbg added the type: bug A confirmed report of unexpected behavior in the application label Feb 11, 2024
grncbg added a commit to grncbg/netbox that referenced this issue Feb 11, 2024
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Feb 12, 2024
@jeremystretch jeremystretch added the severity: low Does not significantly disrupt application functionality, or a workaround is available label Feb 12, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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
2 participants