Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pheus opened this issue Apr 25, 2025 · 2 comments · Fixed by #19345
Closed

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

pheus opened this issue Apr 25, 2025 · 2 comments · Fixed by #19345
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Milestone

Comments

@pheus
Copy link
Contributor

pheus commented Apr 25, 2025

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.

@pheus pheus added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Apr 25, 2025
@pheus
Copy link
Contributor Author

pheus commented Apr 25, 2025

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

@jnovinger jnovinger added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Apr 28, 2025
@jnovinger
Copy link
Member

Thanks, it's all your @pheus !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants