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

Devices already assigned to a Virtual Chassis addable to new VC upon creation #10923

New Issue
Closed
opened 2025-12-29 21:37:47 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:37:47 +01:00
Owner
Copy Link

Originally created by @Azmodeszer on GitHub (Mar 19, 2025).

Originally assigned to: @jeremystretch on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.2.5

Python Version

3.12

Steps to Reproduce

Create a virtual chassis VC1.
Assign one or more devices to it.
Create virtual chassis VC2.
While still at the add form, search for the same member device(s) from step 2.

Expected Behavior

Already assigned devices don't show up in the search or at least an error is shown if you try to save with an already taken object. (the former is the way it works when trying to add already assigned members to a VC after the fact)

Observed Behavior

Objects are reassigned from VC1 to VC2. Any initially designated masters of VC1 are still shown for VC1, even though it now has 0 members.

Originally created by @Azmodeszer on GitHub (Mar 19, 2025). Originally assigned to: @jeremystretch on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.2.5 ### Python Version 3.12 ### Steps to Reproduce Create a virtual chassis VC1. Assign one or more devices to it. Create virtual chassis VC2. While still at the add form, search for the same member device(s) from step 2. ### Expected Behavior Already assigned devices don't show up in the search or at least an error is shown if you try to save with an already taken object. (the former is the way it works when trying to add already assigned members to a VC _after_ the fact) ### Observed Behavior Objects are reassigned from VC1 to VC2. Any initially designated masters of VC1 are still shown for VC1, even though it now has 0 members.
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 21:37:47 +01:00
adam closed this issue 2025-12-29 21:37:47 +01:00
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 severity: low 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#10923
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?