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 a VLAN that has no site assigned to a prefix that has a site assigned #6423

New Issue
Closed
opened 2025-12-29 19:40:32 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:40:32 +01:00
Owner
Copy Link

Originally created by @schmittvictor on GitHub (Apr 29, 2022).

NetBox version

v3.2.1

Python version

3.8

Steps to Reproduce

Assign a VLAN that has no site to a prefix that has a site

Expected Behavior

Assign a VLAN that has no site to a prefix with a site.

Observed Behavior

Can't assign a VLAN that has no site assigned to a prefix that has a site assigned.

The only way to do it is to first assign the VLAN and then assign the site to the prefix.

Originally created by @schmittvictor on GitHub (Apr 29, 2022). ### NetBox version v3.2.1 ### Python version 3.8 ### Steps to Reproduce Assign a VLAN that has no site to a prefix that has a site ### Expected Behavior Assign a VLAN that has no site to a prefix with a site. ### Observed Behavior Can't assign a VLAN that has no site assigned to a prefix that has a site assigned. The only way to do it is to first assign the VLAN and then assign the site to the prefix.
adam added the type: bug label 2025-12-29 19:40:32 +01:00
adam closed this issue 2025-12-29 19:40:33 +01:00
adam commented 2025-12-29 19:40:33 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (May 2, 2022):

Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the feature request template. Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.

@DanSheps commented on GitHub (May 2, 2022): Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the [feature request template](https://github.com/netbox-community/netbox/issues/new?template=feature_request.md). Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.
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 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#6423
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?