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

Rack elevations are offset when racks don't have a facility ID #3568

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

Originally created by @cpmills1975 on GitHub (Apr 14, 2020).

Environment

  • Python version: 3.7.7
  • NetBox version: 2.8.0

Steps to Reproduce

  1. Create a rack with a facility ID
  2. Create another rack without a facility ID
  3. View the elevations view (/dcim/rack-elevations)

Expected Behavior

One assumes the racks are bottom-aligned as this would make sense when say a 42U rack is located next to a 47U rack but U1 in both racks should be aligned regardless of whether a rack has a facility ID or not.

Observed Behavior

The rack with a facility ID appears to be pushed up by the text showing the facility ID. In my browser (Safari) this is about the space of a U meaning U41 in the rack with a facility ID appears level with U42 on the rack that doesn't have a facility ID.

Unfortunately I cannot grab a screen shot of this, or I would.

Originally created by @cpmills1975 on GitHub (Apr 14, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report, and that any plugins have been disabled. --> ### Environment * Python version: 3.7.7 * NetBox version: 2.8.0 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a client library such as pynetbox. --> ### Steps to Reproduce 1. Create a rack with a facility ID 2. Create another rack without a facility ID 3. View the elevations view (/dcim/rack-elevations) <!-- What did you expect to happen? --> ### Expected Behavior One assumes the racks are bottom-aligned as this would make sense when say a 42U rack is located next to a 47U rack but U1 in both racks should be aligned regardless of whether a rack has a facility ID or not. <!-- What happened instead? --> ### Observed Behavior The rack with a facility ID appears to be pushed up by the text showing the facility ID. In my browser (Safari) this is about the space of a U meaning U41 in the rack with a facility ID appears level with U42 on the rack that doesn't have a facility ID. Unfortunately I cannot grab a screen shot of this, or I would.
adam closed this issue 2025-12-29 18:29:56 +01:00
adam commented 2025-12-29 18:29:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 14, 2020):

This is expected behavior; we don't force whitespace where facility IDs are not in use. People generally either use or don't use facility IDs consistently, so this isn't often a problem.

@jeremystretch commented on GitHub (Apr 14, 2020): This is expected behavior; we don't force whitespace where facility IDs are not in use. People generally either use or don't use facility IDs consistently, so this isn't often a problem.
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#3568
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?