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

Breaking virtual chassis does not break cross-member LAG #1791

New Issue
Closed
opened 2025-12-29 17:19:09 +01:00 by adam · 3 comments
adam commented 2025-12-29 17:19:09 +01:00
Owner
Copy Link

Originally created by @candlerb on GitHub (Jun 15, 2018).

Issue type

[ ] Feature request
[X] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: 2.3.3

Description

Here's a way to get into a strange situation where a physical interface on one switch is associated with a LAG on a different switch.

  • Create two switches (testvc1, testvc2) with interfaces g1-g24
  • Rename the interfaces to g1/1-g1/24, g2/1-g2/24 respectively
  • Select them, and create virtual chassis, with testvc1 as master
  • On the master, create a link aggregation interface LAG1
  • Assign g1/1 and g2/1 as members of LAG1
  • Destroy the virtual chassis

Now switch testvc2 interface g2/1 is still associated with LAG1 on testvc1

Originally created by @candlerb on GitHub (Jun 15, 2018). ### Issue type [ ] Feature request <!-- An enhancement of existing functionality --> [X] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Environment * Python version: 3.5.2 * NetBox version: 2.3.3 ### Description Here's a way to get into a strange situation where a physical interface on one switch is associated with a LAG on a different switch. * Create two switches (testvc1, testvc2) with interfaces g1-g24 * Rename the interfaces to g1/1-g1/24, g2/1-g2/24 respectively * Select them, and create virtual chassis, with testvc1 as master * On the master, create a link aggregation interface LAG1 * Assign g1/1 and g2/1 as members of LAG1 * Destroy the virtual chassis Now switch testvc2 interface g2/1 is still associated with LAG1 on testvc1
adam added the type: bugstatus: accepted labels 2025-12-29 17:19:09 +01:00
adam closed this issue 2025-12-29 17:19:09 +01:00
adam commented 2025-12-29 17:19:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 29, 2018):

What's the best way to handle this? Prevent the member from being removed from the VC? Or just automatically remove the interface from the LAG? I'd go with the former.

@jeremystretch commented on GitHub (Jun 29, 2018): What's the best way to handle this? Prevent the member from being removed from the VC? Or just automatically remove the interface from the LAG? I'd go with the former.
adam commented 2025-12-29 17:19:10 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Jun 29, 2018):

I don't have a strong view, as long as the invariant is maintained one way or the other.

@candlerb commented on GitHub (Jun 29, 2018): I don't have a strong view, as long as the invariant is maintained one way or the other.
adam commented 2025-12-29 17:19:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 13, 2019):

Fixed in 462cede863

@jeremystretch commented on GitHub (Dec 13, 2019): Fixed in 462cede8631e45630482d7332a0faa9c274253f8
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 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#1791
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?