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

Unable to assign vlan group to prefix #1365

New Issue
Closed
opened 2025-12-29 16:31:47 +01:00 by adam · 5 comments
adam commented 2025-12-29 16:31:47 +01:00
Owner
Copy Link

Originally created by @will-h on GitHub (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.

Originally created by @will-h on GitHub (Oct 31, 2017). <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. If none of the below apply, please raise your issue for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. ---> ### Issue type [ ] Feature request <!-- Requesting the implementation of a new feature --> [x] Bug report <!-- Reporting unexpected or erroneous behavior --> [ ] Documentation <!-- Proposing a modification to the documentation --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) --> ### Environment * Python version: 3.5.3 * NetBox version: 2.2.2 <!-- BUG REPORTS must include: * A list of the steps needed to reproduce the bug * A description of the expected behavior * Any relevant error messages (screenshots may also help) FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### 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](https://user-images.githubusercontent.com/2152161/32215734-b8cdab7a-be1a-11e7-88e9-aae02f968f4b.png) 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.
adam closed this issue 2025-12-29 16:31:47 +01:00
adam commented 2025-12-29 16:31:48 +01:00
Author
Owner
Copy Link

@maximebrun commented on GitHub (Oct 31, 2017):

Hello,

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

@maximebrun commented on GitHub (Oct 31, 2017): Hello, It seems to be a problem with django-filter 1.1.0. Downgrade to version 1.0.4 fix the problem for me.
adam commented 2025-12-29 16:31:48 +01:00
Author
Owner
Copy Link

@engageant commented on GitHub (Oct 31, 2017):

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.

@engageant commented on GitHub (Oct 31, 2017): I'm having a [similar issue](https://groups.google.com/forum/#!topic/netbox-discuss/lywG382f_NI). 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.
adam commented 2025-12-29 16:31:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 31, 2017):

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.

@jeremystretch commented on GitHub (Oct 31, 2017): > 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.
adam commented 2025-12-29 16:31:49 +01:00
Author
Owner
Copy Link

@will-h commented on GitHub (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 commented on GitHub (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.
adam commented 2025-12-29 16:31:49 +01:00
Author
Owner
Copy Link

@will-h commented on GitHub (Nov 1, 2017):

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

@will-h commented on GitHub (Nov 1, 2017): Back on django_filters 1.1.0, as this problem appears resolved in version 2.2.4 #1671 - see #1649
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
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#1365
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?