Skip to content
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

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

Closed
hotschmaster23 opened this issue Dec 18, 2018 · 6 comments
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@hotschmaster23
Copy link

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

@jeremystretch
Copy link
Member

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

@jeremystretch jeremystretch added the status: revisions needed This issue requires additional information to be actionable label Dec 18, 2018
@hotschmaster23
Copy link
Author

hotschmaster23 commented 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

@rgrueebler
Copy link

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

@baldoarturo
Copy link

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

@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation and removed status: revisions needed This issue requires additional information to be actionable labels Dec 20, 2018
@rgrueebler
Copy link

  • Thank you Jeremy for your great work.

@hotschmaster23
Copy link
Author

thank you very much Jeremy

@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

4 participants