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

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

Closed
shaderecker opened this issue Jun 12, 2024 · 1 comment · Fixed by #16769
Closed

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

shaderecker opened this issue Jun 12, 2024 · 1 comment · Fixed by #16769
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

@shaderecker
Copy link

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.

@shaderecker shaderecker added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Jun 12, 2024
@jeffgdotorg
Copy link
Contributor

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 jeffgdotorg removed the status: needs triage This issue is awaiting triage by a maintainer label Jun 20, 2024
@jeffgdotorg jeffgdotorg removed their assignment Jun 20, 2024
@jeffgdotorg jeffgdotorg added severity: low Does not significantly disrupt application functionality, or a workaround is available status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Jun 20, 2024
@arthanson arthanson self-assigned this Jun 26, 2024
@arthanson arthanson added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Jun 26, 2024
@jeremystretch jeremystretch self-assigned this Jun 30, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 30, 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
4 participants