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

Duplicate MAC address attribute #18456

Closed
Azmodeszer opened this issue Jan 22, 2025 · 2 comments · Fixed by #18450
Closed

Duplicate MAC address attribute #18456

Azmodeszer opened this issue Jan 22, 2025 · 2 comments · Fixed by #18450
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

@Azmodeszer
Copy link
Contributor

Deployment Type

Self-hosted

NetBox Version

v4.2.2

Python Version

3.11

Steps to Reproduce

  1. Go to a device or VM interface table.
  2. Check the available columns.

Expected Behavior

One column: "MAC Address"

Observed Behavior

Two columns: "MAC Address", "Mac address"

Image
Image

dir(Interface) in the Python shell also shows me ...'mac_address', 'mac_addresses',...

So I guess the lowercase one is probably a remnant from a plugin or something? These are the plugins I have currently installed:

  • NetBox Floorplan
  • Reordering Racked Devices
  • NetBox Interface Synchronization
  • NetBox Topology Views
  • NetBox Inventory
  • Document Storage
  • IP Calculator

As far as I can determine, none of them are the culprit, so something that used to be installed maybe? In any case, how to get rid of it?

@Azmodeszer Azmodeszer added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Jan 22, 2025
@bctiemann
Copy link
Contributor

bctiemann commented Jan 22, 2025

Maybe related to #18447 ? At least the fix to that will certainly have some interaction with this behavior.

@DanSheps DanSheps linked a pull request Jan 23, 2025 that will close this issue
@DanSheps
Copy link
Member

I think this will be fixed by merging #18450. Once we merge that can you check the behaviour again?

@DanSheps DanSheps added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Jan 23, 2025
@DanSheps DanSheps self-assigned this Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

Successfully merging a pull request may close this issue.

3 participants