VLAN members list does not include Virtual Machine interfaces #4049

Closed
opened 2025-12-29 18:32:50 +01:00 by adam · 0 comments
Owner

Originally created by @eikef on GitHub (Aug 31, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.8
  • NetBox version: 2.9.2

Steps to Reproduce

  1. Create a VLAN
  2. Create a VM Cluster
  3. Create a virtual machine in said cluster
  4. Create an interface in said virtual machine
  5. Assign previously created VLAN as Access to VM interface
  6. Navigate to /ipam/vlans/XXX/members/

The Virtual Machine interface should be listed amongst the members of the VLAN

The interface is not listed as a member of the VLAN

Originally created by @eikef on GitHub (Aug 31, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6.8 * NetBox version: 2.9.2 <!-- 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. Create a VLAN 2. Create a VM Cluster 3. Create a virtual machine in said cluster 4. Create an interface in said virtual machine 5. Assign previously created VLAN as Access to VM interface 3. Navigate to /ipam/vlans/XXX/members/ <!-- What did you expect to happen? --> The Virtual Machine interface should be listed amongst the members of the VLAN <!-- What happened instead? --> The interface is not listed as a member of the VLAN
adam added the type: bugstatus: accepted labels 2025-12-29 18:32:50 +01:00
adam closed this issue 2025-12-29 18:32:51 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4049