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

Links to LAG ports should be (more) absolute #3932

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

Originally created by @cpmills1975 on GitHub (Aug 3, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.8
  • NetBox version: 2.9-beta1

Steps to Reproduce

  1. On a virtual chassis master, create a LAG interface
  2. On a virtual chassis member, other than the master, edit an interface to make it part of the LAG previously defined
  3. View the interfaces list for the chassis member and, next to the physical interface that is part of the LAG, observe that the link behind the LAG name points to #interface_lagname. On chassis members that are not the master, this link goes nowhere.

Expected Behavior

With the move to separate out pages of interfaces to individual chassis members rather than display them all on the master's page, the link to the LAG interface needs to point to the device where the LAG is defined e.g. rather than just #interface_ae0, the link should be to /dcim/devices/1/#interface_ae0 so clicking on it takes the viewer to the definition of the LAG.

Observed Behavior

The link points to #interface_ae0 regardless of the chassis member that is displaying the child interface of the LAG. Consequently, if the LAG is not defined on the same physical device, the link goes nowhere.

Originally created by @cpmills1975 on GitHub (Aug 3, 2020). Originally assigned to: @jeremystretch on GitHub. <!-- 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.6.8 * NetBox version: 2.9-beta1 <!-- 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. On a virtual chassis master, create a LAG interface 2. On a virtual chassis member, other than the master, edit an interface to make it part of the LAG previously defined 3. View the interfaces list for the chassis member and, next to the physical interface that is part of the LAG, observe that the link behind the LAG name points to #interface_lagname. On chassis members that are not the master, this link goes nowhere. <!-- What did you expect to happen? --> ### Expected Behavior With the move to separate out pages of interfaces to individual chassis members rather than display them all on the master's page, the link to the LAG interface needs to point to the device where the LAG is defined e.g. rather than just #interface_ae0, the link should be to /dcim/devices/1/#interface_ae0 so clicking on it takes the viewer to the definition of the LAG. <!-- What happened instead? --> ### Observed Behavior The link points to #interface_ae0 regardless of the chassis member that is displaying the child interface of the LAG. Consequently, if the LAG is not defined on the same physical device, the link goes nowhere.
adam added the type: bugstatus: acceptedbeta labels 2025-12-29 18:32:09 +01:00
adam closed this issue 2025-12-29 18:32:09 +01:00
adam commented 2025-12-29 18:32:09 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 3, 2020):

Thank you for taking the time to open issues for these little things! They're very easy for devs like myself to miss while in the weeds.

@jeremystretch commented on GitHub (Aug 3, 2020): Thank you for taking the time to open issues for these little things! They're very easy for devs like myself to miss while in the weeds.
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 beta 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#3932
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?