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

Cannot distinguish between master and standby device of Virtual Chassis #9833

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

Originally created by @shaderecker on GitHub (Jun 12, 2024).

Originally assigned to: @arthanson, @jeremystretch on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.0.5

Python Version

3.11

Steps to Reproduce

  1. Have a virtual chassis with a master and standby device.
  2. Open one (or both) of the devices.
  3. Check in the Virtual Chassis section of the device.
  4. See that the current device isn't highlighted there.

Expected Behavior

A visible visual distinction/highligting of the current device in the virtual chassis section

Observed Behavior

No highlighting of the current device in the Virtual Chassis section.
This is a regression in Netbox v4.

Originally created by @shaderecker on GitHub (Jun 12, 2024). Originally assigned to: @arthanson, @jeremystretch on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.0.5 ### Python Version 3.11 ### Steps to Reproduce 1. Have a virtual chassis with a master and standby device. 2. Open one (or both) of the devices. 3. Check in the Virtual Chassis section of the device. 4. See that the current device isn't highlighted there. ### Expected Behavior A visible visual distinction/highligting of the current device in the virtual chassis section ### Observed Behavior No highlighting of the current device in the Virtual Chassis section. This is a regression in Netbox v4.
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 21:23:22 +01:00
adam closed this issue 2025-12-29 21:23:23 +01:00
adam commented 2025-12-29 21:23:23 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Jun 20, 2024):

Thanks for reporting this problem. I agree it's a regression.

For the benefit of whomever picks it up, here are screenshots illustrating the highlighting in 3.7.8:
image

And the lack of it in the same install upgraded to 4.0.5:
image

The fix may be a straightforward CSS change.

@jeffgdotorg commented on GitHub (Jun 20, 2024): Thanks for reporting this problem. I agree it's a regression. For the benefit of whomever picks it up, here are screenshots illustrating the highlighting in 3.7.8: ![image](https://github.com/netbox-community/netbox/assets/1209268/d918a4e3-a771-48ef-b202-aa84b862cc01) And the lack of it in the same install upgraded to 4.0.5: ![image](https://github.com/netbox-community/netbox/assets/1209268/abb8513e-0de0-489f-8cc9-9e84eba13a2c) The fix may be a straightforward CSS change.
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 severity: low status: accepted 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#9833
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?