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

Unable to assign vlan group to prefix #1663

Closed
will-h opened this issue Oct 31, 2017 · 5 comments
Closed

Unable to assign vlan group to prefix #1663

will-h opened this issue Oct 31, 2017 · 5 comments

Comments

@will-h
Copy link

will-h commented Oct 31, 2017

Issue type

[ ] Feature request
[x] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.3
  • NetBox version: 2.2.2

Description

Recently upgraded from 2.0.7 to 2.2.2.

After upgrading, I can no longer set a vlan group on a prefix. I can select the appropriate vlan group but this doesn't persist when i click 'Update'

screen shot 2017-10-31 at 09 01 16

This means I'm unable to associate that IP prefix with a vlan. I've tried disassociating existing prefixes from a vlan, and am then unable to add them.

@maximebrun
Copy link

Hello,

It seems to be a problem with django-filter 1.1.0. Downgrade to version 1.0.4 fix the problem for me.

@engageant
Copy link

I'm having a similar issue. I downgraded django-filter to 1.0.4 and it doesn't help. Unsure if these issues are related, so I figured I'd tack on to this before opening a new issue.

@jeremystretch
Copy link
Member

After upgrading, I can no longer set a vlan group on a prefix.

NetBox has never supported assigning a prefix to a VLAN group. That wouldn't make sense. A prefix can only be assigned to a single VLAN. The VLAN group field is only there to help choose a VLAN.

@will-h
Copy link
Author

will-h commented Nov 1, 2017

@jeremystretch Apologies, my description of the problem was incorrect. The net result is the same, though - I was unable to select a vlan and associate it with a prefix.

@maximebrun thank you, downgrading django_filters ("pip3 install django_filter==1.0.4") resolved the problem for me.

@will-h
Copy link
Author

will-h commented Nov 1, 2017

Back on django_filters 1.1.0, as this problem appears resolved in version 2.2.4 #1671 - see #1649

@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants