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

UI problem with vlan assignment for prefixes. #5937

New Issue
Closed
opened 2025-12-29 19:34:30 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:34:30 +01:00
Owner
Copy Link

Originally created by @empusas on GitHub (Jan 12, 2022).

NetBox version

v3.1.5

Python version

3.9

Steps to Reproduce

  1. create a VLAN, prefix and assign to site and site group
  2. create vlan group and set scope to site-group(leave site empty)
  3. try to assign the vlan to the prefix.
  4. you can select the vlan group, but the VLAN list is still empty
  5. the VLAN will not show up until you remove the site(leave the site group) from the prefix.
  6. when the vlan and vlan group is selected you can select the site and save the prefix.

I have used my own 3.1.5 instance and verified with the demo.netbox. same issue.

image

image

image

image

Expected Behavior

All vlan/vlan groups should be in the dropdown if only the site group matches.

Use case: If you have a multisite, a VLAN might be spanned across both sites and common distinguisher is the site group, not the specific site.

Observed Behavior

If the vlan is part of a vlan group and the the scope of the vlan group is set to site-group only(site is blank) it will not show up for selection.

Originally created by @empusas on GitHub (Jan 12, 2022). ### NetBox version v3.1.5 ### Python version 3.9 ### Steps to Reproduce 1. create a VLAN, prefix and assign to site and site group 2. create vlan group and set scope to site-group(leave site empty) 3. try to assign the vlan to the prefix. 4. you can select the vlan group, but the VLAN list is still empty 5. the VLAN will not show up until you remove the site(leave the site group) from the prefix. 6. when the vlan and vlan group is selected you can select the site and save the prefix. I have used my own 3.1.5 instance and verified with the demo.netbox. same issue. ![image](https://user-images.githubusercontent.com/3153453/149194515-2de3935a-8bd1-47e1-b5fd-80b9830ff167.png) ![image](https://user-images.githubusercontent.com/3153453/149194808-c66454be-b70e-41bb-bce0-71d85ac6ea73.png) ![image](https://user-images.githubusercontent.com/3153453/149195016-acf4cc4c-9985-4e26-959d-f554ede537c4.png) ![image](https://user-images.githubusercontent.com/3153453/149195016-acf4cc4c-9985-4e26-959d-f554ede537c4.png) ### Expected Behavior All vlan/vlan groups should be in the dropdown if only the site group matches. Use case: If you have a multisite, a VLAN might be spanned across both sites and common distinguisher is the site group, not the specific site. ### Observed Behavior If the vlan is part of a vlan group and the the scope of the vlan group is set to site-group only(site is blank) it will not show up for selection.
adam added the type: bugstatus: needs ownerpending closure labels 2025-12-29 19:34:30 +01:00
adam closed this issue 2025-12-29 19:34:30 +01:00
adam commented 2025-12-29 19:34:30 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 20, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 20, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:34:30 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 19, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Apr 19, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner 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#5937
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?