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

Unable to tag vlan to multisite cluster #6218

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

Originally created by @nomad-cyanide on GitHub (Mar 16, 2022).

NetBox version

v.3.1.9

Python version

3.8

Steps to Reproduce

  1. Create 2 sites (test-site1 and test-site2)
  2. Create 1 Site-group (test-site-group) containing test-site1 and test-site2
  3. Create 1 vlan-group (test-vlan-group1) with scope site-group = test-site-group.
  4. Create 1 vlan (test-vlan1) in test-vlan-group1.
  5. Create 2 devices (test-device1 and test-device2) One device for each site (e.g. test-device belongs to test-site1)
  6. Create 1 Cluster (test-cluster1) and add the 2 test-devices to it. Since each device belongs to different sites, you cannot set a site for the cluster, so leave that as "none"
  7. create a Virtual Machine (test-vm-1) in test-cluster1 and add an interface to that vm (mgmt)
  8. Edit the mgmt interface on test-vm-1, set 802.1Q Mode to "Access" and select the vlan-group "test-vlan-group1".
  9. This is where I would expect to be able to select test-vlan-1 from vlan-group test-vlan-group1.
    Only if I remove one of the devices from the cluster and set a site (e.g. test-site1) on the cluster, am I able to select a vlan from the vlan-group test-vlan-group1

The reason that I need to be able to do this, is because clusters are multisite, connected with L2 vlans.
We could define a site-group covering both sites, but then we would have to set all devices to that (multi)site, which in turn does show the correct information about where the devices are physically placed.

Expected Behavior

I would expect to be able to select the vlan from the vlan-group I select from the interface GUI.

It looks like this might only be a GUI problem, as I can still tag vlans using the API.

Observed Behavior

I am not able to select a vlan in GUI.

Originally created by @nomad-cyanide on GitHub (Mar 16, 2022). ### NetBox version v.3.1.9 ### Python version 3.8 ### Steps to Reproduce 1. Create 2 sites (test-site1 and test-site2) 2. Create 1 Site-group (test-site-group) containing test-site1 and test-site2 3. Create 1 vlan-group (test-vlan-group1) with scope site-group = test-site-group. 4. Create 1 vlan (test-vlan1) in test-vlan-group1. 5. Create 2 devices (test-device1 and test-device2) One device for each site (e.g. test-device belongs to test-site1) 6. Create 1 Cluster (test-cluster1) and add the 2 test-devices to it. Since each device belongs to different sites, you cannot set a site for the cluster, so leave that as "none" 7. create a Virtual Machine (test-vm-1) in test-cluster1 and add an interface to that vm (mgmt) 8. Edit the mgmt interface on test-vm-1, set 802.1Q Mode to "Access" and select the vlan-group "test-vlan-group1". 9. This is where I would expect to be able to select test-vlan-1 from vlan-group test-vlan-group1. Only if I remove one of the devices from the cluster and set a site (e.g. test-site1) on the cluster, am I able to select a vlan from the vlan-group test-vlan-group1 The reason that I need to be able to do this, is because clusters are multisite, connected with L2 vlans. We could define a site-group covering both sites, but then we would have to set all devices to that (multi)site, which in turn does show the correct information about where the devices are physically placed. ### Expected Behavior I would expect to be able to select the vlan from the vlan-group I select from the interface GUI. It looks like this might only be a GUI problem, as I can still tag vlans using the API. ### Observed Behavior I am not able to select a vlan in GUI.
adam added the type: bug label 2025-12-29 19:38:09 +01:00
adam closed this issue 2025-12-29 19:38:09 +01:00
adam commented 2025-12-29 19:38:10 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Mar 18, 2022):

This would be more appropriate as a feature request, and there is already a FR for this specific issue: #6429

@DanSheps commented on GitHub (Mar 18, 2022): This would be more appropriate as a feature request, and there is already a FR for this specific issue: #6429
adam commented 2025-12-29 19:38:10 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Mar 18, 2022):

Duplicate of #6429

@DanSheps commented on GitHub (Mar 18, 2022): Duplicate of #6429
adam commented 2025-12-29 19:38:10 +01:00
Author
Owner
Copy Link

@nomad-cyanide commented on GitHub (Mar 21, 2022):

then how come it seems to work, when tagging interfaces via the API?

@nomad-cyanide commented on GitHub (Mar 21, 2022): then how come it seems to work, when tagging interfaces via the API?
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 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#6218
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?