VM Interface: Error Fetching Options for field 'untagged_vlan' #7011

Closed
opened 2025-12-29 19:47:51 +01:00 by adam · 0 comments
Owner

Originally created by @t8simon on GitHub (Sep 22, 2022).

Originally assigned to: @arthanson, @jeremystretch on GitHub.

NetBox version

v3.3.4

Python version

3.10

Steps to Reproduce

  1. Create a VM and assign it only to a Site, not a Cluster
  2. Create a Interface for the VM
  3. Scroll down, select 802.1Q Mode: "Access"
  4. Open the "Untagged VLAN" Dropdown

Expected Behavior

A short error message with a hint on the error. Or the possibility to select a VLAN when no Cluster is assigned to the VM (if that makes any sense).

Observed Behavior

A very long error message with visible html code appears.
Screenshot

Originally created by @t8simon on GitHub (Sep 22, 2022). Originally assigned to: @arthanson, @jeremystretch on GitHub. ### NetBox version v3.3.4 ### Python version 3.10 ### Steps to Reproduce 1. Create a VM and assign it only to a Site, not a Cluster 2. Create a Interface for the VM 3. Scroll down, select 802.1Q Mode: "Access" 4. Open the "Untagged VLAN" Dropdown ### Expected Behavior A short error message with a hint on the error. Or the possibility to select a VLAN when no Cluster is assigned to the VM (if that makes any sense). ### Observed Behavior A very long error message with visible html code appears. ![Screenshot](https://user-images.githubusercontent.com/104978710/191734654-845f892e-fdd0-41ab-8a3f-751b10ba1c30.png)
adam added the type: bugstatus: accepted labels 2025-12-29 19:47:51 +01:00
adam closed this issue 2025-12-29 19:47: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#7011