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

VMInterface template does not display Q-in-Q Service VLAN #11085

New Issue
Closed
opened 2025-12-29 21:40:05 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:40:05 +01:00
Owner
Copy Link

Originally created by @pheus on GitHub (Apr 25, 2025).

Originally assigned to: @pheus on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.2.8

Python Version

3.10

Steps to Reproduce

  1. Create a VLAN SVLAN11 and assign it the Q-in-Q role Service.
  2. Create a virtual machine VM1
  3. Navigate to a virtual machine and add a VM Interface eth0.
  4. Edit the VM Interface eth0, assign the 802.1Q role Q-in-Q and assign the Q-in-Q Service VLAN SVLAN11 under the “Q-in-Q Service VLAN” field.
  5. Save the interface.
  6. View the VMInterface detail page.

Expected Behavior

The Q-in-Q Service VLAN should be displayed in the VMInterface detail view.

Observed Behavior

The Q-in-Q Service VLAN is not displayed in the VMInterface detail page, even though it is assigned and stored in the database.

Originally created by @pheus on GitHub (Apr 25, 2025). Originally assigned to: @pheus on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.2.8 ### Python Version 3.10 ### Steps to Reproduce 1. Create a VLAN `SVLAN11` and assign it the Q-in-Q role *Service*. 2. Create a virtual machine `VM1` 3. Navigate to a virtual machine and add a VM Interface `eth0`. 4. Edit the VM Interface `eth0`, assign the 802.1Q role `Q-in-Q` and assign the Q-in-Q Service VLAN `SVLAN11` under the “Q-in-Q Service VLAN” field. 5. Save the interface. 6. View the VMInterface detail page. ### Expected Behavior The Q-in-Q Service VLAN should be displayed in the `VMInterface` detail view. ### Observed Behavior The Q-in-Q Service VLAN is not displayed in the `VMInterface` detail page, even though it is assigned and stored in the database.
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 21:40:05 +01:00
adam closed this issue 2025-12-29 21:40:05 +01:00
adam commented 2025-12-29 21:40:06 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Apr 25, 2025):

I'd be happy to contribute this, if accepted!

@pheus commented on GitHub (Apr 25, 2025): I'd be happy to contribute this, if accepted!
adam commented 2025-12-29 21:40:07 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Apr 28, 2025):

Thanks, it's all your @pheus !

@jnovinger commented on GitHub (Apr 28, 2025): Thanks, it's all your @pheus !
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 severity: low 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#11085
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?