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

Assigning Vlans in Vlangroups to prefixes no more possible after upgrade to newest version #2221

New Issue
Closed
opened 2025-12-29 17:23:52 +01:00 by adam · 6 comments
adam commented 2025-12-29 17:23:52 +01:00
Owner
Copy Link

Originally created by @hotschmaster23 on GitHub (Dec 18, 2018).

Environment

  • Python version: 3.6
  • NetBox version: 2.5.1

Steps to Reproduce

Assigning Vlans in Vlangroups to prefixes no more possible after upgrade to newest version.
We have a lot of datacenters and assign to every datacenterlocation one VLAN Group with same VLANS. After that we assign our Prefixes (Private and Public) to these different Groups and Vlans.
After upgrade to newest version of netbox 2.5.1, you are able to choose the Vlan group when a new Prefix is created, but no Vlan choice is possible in the dropdown menu, but the vlans are in these groups.

Expected Behavior

Please resolve it that this function is possible again

Observed Behavior

Originally created by @hotschmaster23 on GitHub (Dec 18, 2018). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6 * NetBox version: 2.5.1 <!-- Describe in detail the steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). --> ### Steps to Reproduce Assigning Vlans in Vlangroups to prefixes no more possible after upgrade to newest version. We have a lot of datacenters and assign to every datacenterlocation one VLAN Group with same VLANS. After that we assign our Prefixes (Private and Public) to these different Groups and Vlans. After upgrade to newest version of netbox 2.5.1, you are able to choose the Vlan group when a new Prefix is created, but no Vlan choice is possible in the dropdown menu, but the vlans are in these groups. <!-- What did you expect to happen? --> ### Expected Behavior Please resolve it that this function is possible again <!-- What happened instead? --> ### Observed Behavior
adam added the type: bugstatus: accepted labels 2025-12-29 17:23:52 +01:00
adam closed this issue 2025-12-29 17:23:52 +01:00
adam commented 2025-12-29 17:23:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 18, 2018):

Please list the exact steps that someone can take to reproduce this issue, beginning with the creation of VLANs.

@jeremystretch commented on GitHub (Dec 18, 2018): Please list the exact steps that someone can take to reproduce this issue, beginning with the creation of VLANs.
adam commented 2025-12-29 17:23:53 +01:00
Author
Owner
Copy Link

@hotschmaster23 commented on GitHub (Dec 19, 2018):

Steps to reproduce this issue:
1.) Click on menu entry IPAM and navigate to "Vlan Groups", choose "+" to add a VLAN Group.
2.) Create a new Vlan Group Name
3.) Click on menu entry IPAM, navigate to "VLANS" and click on "+" to new VLANS for this new VLAN Group.
4.) In the field VLAN navigate to Group and click on the drop down menu to choose the new created VLAN Group
5.) After the new VLANs and VLAN Group are created go to VLAN and click on "+Add a prefix" in the field Prefixes on the right site.
6.) Add a Prefix, to reproduce this issue, choose a dummy Prefix like 192.168.0.1/24
7.) Navigate to Site/VLAN Assignment and select the new VLAN Group which you created in step 1.)
8.) Now you will notice that no VLAN can be selected in the drop down menu "VLAN", only a "+" character will be displayed also when you wait 10 minutes no vlan will be displayed
This happens with every VLAN Group we have and with every constellation

  • with or without Tenancy -> Tenant Group -> Tenant
  • with or without Site in Site/VLAN Assignment
  • with every Prefix and we are a service provider who has a lot of prefixes

hope this helps to reproduce the issue

@hotschmaster23 commented on GitHub (Dec 19, 2018): Steps to reproduce this issue: 1.) Click on menu entry IPAM and navigate to "Vlan Groups", choose "+" to add a VLAN Group. 2.) Create a new Vlan Group Name 3.) Click on menu entry IPAM, navigate to "VLANS" and click on "+" to new VLANS for this new VLAN Group. 4.) In the field VLAN navigate to Group and click on the drop down menu to choose the new created VLAN Group 5.) After the new VLANs and VLAN Group are created go to VLAN and click on "+Add a prefix" in the field Prefixes on the right site. 6.) Add a Prefix, to reproduce this issue, choose a dummy Prefix like 192.168.0.1/24 7.) Navigate to Site/VLAN Assignment and select the new VLAN Group which you created in step 1.) 8.) Now you will notice that no VLAN can be selected in the drop down menu "VLAN", only a "+" character will be displayed also when you wait 10 minutes no vlan will be displayed This happens with every VLAN Group we have and with every constellation - with or without Tenancy -> Tenant Group -> Tenant - with or without Site in Site/VLAN Assignment - with every Prefix and we are a service provider who has a lot of prefixes hope this helps to reproduce the issue
adam commented 2025-12-29 17:23:53 +01:00
Author
Owner
Copy Link

@rgrueebler commented on GitHub (Dec 19, 2018):

Hi everyone,

I have the same issue. When I navigate to IPAM -> Prefixes -> select a prefix -> click "Edit this prefix".
Under the section "Site/VLAN Assignment" I can select a VLAN group but I am unable to select a specific VLAN in that group.
I expect that I can assign a VLAN-group and a VLAN to a prefix. This was possible in the previous versions.

Best regards
Remo

@rgrueebler commented on GitHub (Dec 19, 2018): Hi everyone, I have the same issue. When I navigate to IPAM -> Prefixes -> select a prefix -> click "Edit this prefix". Under the section "Site/VLAN Assignment" I can select a VLAN group but I am unable to select a specific VLAN in that group. I expect that I can assign a VLAN-group and a VLAN to a prefix. This was possible in the previous versions. Best regards Remo
adam commented 2025-12-29 17:23:53 +01:00
Author
Owner
Copy Link

@baldoarturo commented on GitHub (Dec 19, 2018):

I can confirm this happens on v2.5.1

image

It looks like the issue is on the template rendering, I have no way to debug it now, but I tried to create the prefix using the Import option, using the vlan_group and vlan_vid fields

@baldoarturo commented on GitHub (Dec 19, 2018): I can confirm this happens on v2.5.1 ![image](https://user-images.githubusercontent.com/30608412/50236493-5015db00-0399-11e9-8cf1-aef6a01cc5cb.png) It looks like the issue is on the template rendering, I have no way to debug it now, but I tried to create the prefix using the Import option, using the vlan_group and vlan_vid fields
adam commented 2025-12-29 17:23:53 +01:00
Author
Owner
Copy Link

@rgrueebler commented on GitHub (Dec 21, 2018):

  • Thank you Jeremy for your great work.
@rgrueebler commented on GitHub (Dec 21, 2018): - Thank you Jeremy for your great work.
adam commented 2025-12-29 17:23:54 +01:00
Author
Owner
Copy Link

@hotschmaster23 commented on GitHub (Dec 21, 2018):

thank you very much Jeremy

@hotschmaster23 commented on GitHub (Dec 21, 2018): thank you very much Jeremy
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 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#2221
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?