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

Edit Interface does not select correct LAG interfaces #5344

New Issue
Closed
opened 2025-12-29 19:26:55 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:26:55 +01:00
Owner
Copy Link

Originally created by @doogienz on GitHub (Sep 8, 2021).

NetBox version

v3.0.1

Python version

3.8

Steps to Reproduce

  1. Create interface on device with Type 'Link Aggregation Group (LAG)' and create
  2. Select Interface from main interface screen of device to individually add to LAG group
  3. Edit Interface from within interface detail screen
  4. LAG Interface input includes random LAG groups - sometimes from the device, but mostly not.

Expected Behavior

Have a list of LAG interfaces from this device. You are able to work around by editing the interface in bulk edit mode, which selects the correct LAG interfaces.

Observed Behavior

LAG interface selection includes randomly selected LAG devices, sometimes from this device and sometimes not.

Originally created by @doogienz on GitHub (Sep 8, 2021). ### NetBox version v3.0.1 ### Python version 3.8 ### Steps to Reproduce 1. Create interface on device with Type 'Link Aggregation Group (LAG)' and create 2. Select Interface from main interface screen of device to individually add to LAG group 3. Edit Interface from within interface detail screen 4. LAG Interface input includes random LAG groups - sometimes from the device, but mostly not. ### Expected Behavior Have a list of LAG interfaces from this device. You are able to work around by editing the interface in bulk edit mode, which selects the correct LAG interfaces. ### Observed Behavior LAG interface selection includes randomly selected LAG devices, sometimes from this device and sometimes not.
adam closed this issue 2025-12-29 19:26:55 +01:00
adam commented 2025-12-29 19:26:55 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 8, 2021):

Please revise your post above to provide detailed reproduction steps, beginning with the creation of the interfaces.

@jeremystretch commented on GitHub (Sep 8, 2021): Please revise your post above to provide detailed reproduction steps, beginning with the creation of the interfaces.
adam commented 2025-12-29 19:26:56 +01:00
Author
Owner
Copy Link

@doogienz commented on GitHub (Sep 8, 2021):

Updated with more detail.

@doogienz commented on GitHub (Sep 8, 2021): Updated with more detail.
adam commented 2025-12-29 19:26:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 8, 2021):

I'm not able to replicate this on v3.0.1. I only see LAG interfaces from the assigned device in the list, and I confirmed that the API request being made to retrieve this is filtered by device_id as expected.

@jeremystretch commented on GitHub (Sep 8, 2021): I'm not able to replicate this on v3.0.1. I only see LAG interfaces from the assigned device in the list, and I confirmed that the API request being made to retrieve this is filtered by `device_id` as expected.
adam commented 2025-12-29 19:26:56 +01:00
Author
Owner
Copy Link

@doogienz commented on GitHub (Sep 8, 2021):

When requests are made to the API - I'm getting results from other devices - i.e. the device_id here is 300 but this is what is occuring on all devices:

/dcim/interfaces/edit/?device=300&return_url=/dcim/devices/300/interfaces/ is actually retrieving info from device 46

/api/dcim/interfaces/?brief=true&device_id=46
/api/dcim/interfaces/?brief=true&device_id=46&type=lag

I'm getting random results though, the device ID selected is never consistent

Sounds like something might be wrong with our install :(

@doogienz commented on GitHub (Sep 8, 2021): When requests are made to the API - I'm getting results from other devices - i.e. the device_id here is 300 but this is what is occuring on all devices: `/dcim/interfaces/edit/?device=300&return_url=/dcim/devices/300/interfaces/` is actually retrieving info from device 46 ``` /api/dcim/interfaces/?brief=true&device_id=46 /api/dcim/interfaces/?brief=true&device_id=46&type=lag ``` I'm getting random results though, the device ID selected is never consistent Sounds like something might be wrong with our install :(
adam commented 2025-12-29 19:26:56 +01:00
Author
Owner
Copy Link

@doogienz commented on GitHub (Sep 8, 2021):

Rebuild of virtual environment cleared issue.

@doogienz commented on GitHub (Sep 8, 2021): Rebuild of virtual environment cleared issue.
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#5344
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?