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

Untagged vlan field pre-populates with first available option #2901

New Issue
Closed
opened 2025-12-29 18:23:15 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:23:15 +01:00
Owner
Copy Link

Originally created by @rendxq on GitHub (Sep 24, 2019).

Environment

Steps to Reproduce

  1. Upgrade NETBOX docker container from v2.6.3 to v2.6.4
  2. Device -> Add interface -> 802.1Q (Tagged)

Expected Behavior

"Untagged vlan" fiel has to be empty (------).
image

Observed Behavior

Into "Untagged vlan" fiel fills with random vlanID.
Also if I edit some vlan-interface that had been created before I see vlanID into "Untagged vlan" fiel which I didn't add to.
image

Originally created by @rendxq on GitHub (Sep 24, 2019). ### Environment * Docker containers I use that docker-coppose file https://github.com/netbox-community/netbox-docker/blob/master/docker-compose.yml ### Steps to Reproduce 1. Upgrade NETBOX docker container from v2.6.3 to v2.6.4 2. Device -> Add interface -> 802.1Q (Tagged) <!-- What did you expect to happen? --> ### Expected Behavior "Untagged vlan" fiel has to be empty (------). ![image](https://user-images.githubusercontent.com/27946443/65485536-59097f00-decc-11e9-93ed-b40a2cfe14df.png) <!-- What happened instead? --> ### Observed Behavior Into "Untagged vlan" fiel fills with random vlanID. Also if I edit some vlan-interface that had been created before I see vlanID into "Untagged vlan" fiel which I didn't add to. ![image](https://user-images.githubusercontent.com/27946443/65485868-3035b980-decd-11e9-86fa-2f58397c215a.png)
adam added the type: bugstatus: accepted labels 2025-12-29 18:23:15 +01:00
adam closed this issue 2025-12-29 18:23:15 +01:00
adam commented 2025-12-29 18:23:16 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Sep 24, 2019):

It appears to be taking the first vlan, I did not encounter this in testing but I have confirmed it.

Going to work on this right now.

@DanSheps commented on GitHub (Sep 24, 2019): It appears to be taking the first vlan, I did not encounter this in testing but I have confirmed it. Going to work on this right now.
adam commented 2025-12-29 18:23:16 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Sep 24, 2019):

This has been fixed, you can git cherry-pick 8996c53 if you need it to be resolved urgently.

@DanSheps commented on GitHub (Sep 24, 2019): This has been fixed, you can `git cherry-pick 8996c53` if you need it to be resolved urgently.
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#2901
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?