VC Member Interfaces Missing from Cable Add View #11257

Closed
opened 2025-12-29 21:42:35 +01:00 by adam · 4 comments
Owner

Originally created by @AesoSpadez on GitHub (Jun 4, 2025).

Originally assigned to: @DanSheps on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.2.6

Python Version

3.11

Steps to Reproduce

  1. Create a Device Type (Test Device Type)
  2. Add a few Interfaces to the Device Type
  3. Create a Device from the new Device Type (Test Device 1)
  4. Create two more Devices from the Device Type (Test Device 2, Test Device 3)
  5. Rename the interfaces on Test Device 3 for uniqueness
  6. Create a Virtual Chassis from Test Devices 2 and 3 (start position 0, position 0 is VC master)
  7. Go to the Test Device 1 Device, open the Interfaces tab
  8. Click the 'add cable' icon for an interface
  9. Select the VC Master (Test Device 2) for the B-side interface
  10. Open the interface list

Expected Behavior

The interface list should contain all VC member interfaces when selecting the VC master device for the B-side device.

Observed Behavior

The interface list only shows interfaces directly associated with the VC master device.

Originally created by @AesoSpadez on GitHub (Jun 4, 2025). Originally assigned to: @DanSheps on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.2.6 ### Python Version 3.11 ### Steps to Reproduce 1. Create a Device Type (Test Device Type) 2. Add a few Interfaces to the Device Type 3. Create a Device from the new Device Type (Test Device 1) 4. Create two more Devices from the Device Type (Test Device 2, Test Device 3) 5. Rename the interfaces on Test Device 3 for uniqueness 6. Create a Virtual Chassis from Test Devices 2 and 3 (start position 0, position 0 is VC master) 7. Go to the Test Device 1 Device, open the Interfaces tab 8. Click the 'add cable' icon for an interface 9. Select the VC Master (Test Device 2) for the B-side interface 10. Open the interface list ### Expected Behavior The interface list should contain all VC member interfaces when selecting the VC master device for the B-side device. ### Observed Behavior The interface list only shows interfaces directly associated with the VC master device.
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 21:42:35 +01:00
adam closed this issue 2025-12-29 21:42:35 +01:00
Author
Owner

@AesoSpadez commented on GitHub (Jun 4, 2025):

We observed this in our prod NetBox instance, and it's reproducible in v4.3.1 as well.

@AesoSpadez commented on GitHub (Jun 4, 2025): We observed this in our prod NetBox instance, and it's reproducible in v4.3.1 as well.
Author
Owner

@jnovinger commented on GitHub (Jun 5, 2025):

This could probably be achieved by making judicious use of the InterfaceFilterSet.virtual_chassis_member_id filter.

@jnovinger commented on GitHub (Jun 5, 2025): This could probably be achieved by making judicious use of the [`InterfaceFilterSet.virtual_chassis_member_id` filter](https://github.com/netbox-community/netbox/blob/0e689010225a14770f1dec5390de49ca43a0960c/netbox/dcim/filtersets.py#L1893-L1897).
Author
Owner

@DanSheps commented on GitHub (Aug 7, 2025):

Was pretty sure I fixed this once already, is this a regression?

@DanSheps commented on GitHub (Aug 7, 2025): Was pretty sure I fixed this once already, is this a regression?
Author
Owner

@DanSheps commented on GitHub (Aug 7, 2025):

Similar: #11478 looks like we (I) was supposed to fix this and went off in a tangent

@DanSheps commented on GitHub (Aug 7, 2025): Similar: #11478 looks like we (I) was supposed to fix this and went off in a tangent
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11257