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

Can't assign VLANs to interfaces #1615

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

Originally created by @patrick7 on GitHub (Mar 9, 2018).

Issue type

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

Environment

  • Python version: 2.7.13-2
  • NetBox version: 2.3.1

Description

I select VLANs which should be tagged on the interface and click Update. Netbox complains "Select a valid choice. X is not one of the available choices."

Originally created by @patrick7 on GitHub (Mar 9, 2018). ### Issue type [ ] Feature request <!-- An enhancement of existing functionality --> [x] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Environment * Python version: 2.7.13-2 * NetBox version: 2.3.1 ### Description I select VLANs which should be tagged on the interface and click Update. Netbox complains "Select a valid choice. X is not one of the available choices."
adam added the type: bugstatus: accepted labels 2025-12-29 16:33:31 +01:00
adam closed this issue 2025-12-29 16:33:31 +01:00
adam commented 2025-12-29 16:33:31 +01:00
Author
Owner
Copy Link

@Armadill0 commented on GitHub (Mar 9, 2018):

I can confirm that.

@Armadill0 commented on GitHub (Mar 9, 2018): I can confirm that.
adam commented 2025-12-29 16:33:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 9, 2018):

This was resolved as part of the work on #1952.

@jeremystretch commented on GitHub (Mar 9, 2018): This was resolved as part of the work on #1952.
adam commented 2025-12-29 16:33:32 +01:00
Author
Owner
Copy Link

@scotty00X commented on GitHub (Mar 16, 2018):

Hi,
I have the latest commit from release v2.3.1including the merge pull request #1937 running. But I still observe the same behavior
image

Regards,
Henrik

@scotty00X commented on GitHub (Mar 16, 2018): Hi, I have the latest commit from release v2.3.1including the merge pull request #1937 running. But I still observe the same behavior ![image](https://user-images.githubusercontent.com/37411806/37519201-880d3cd0-2918-11e8-92d2-fa8dd9bad204.png) Regards, Henrik
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#1615
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?