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

An error was reported when Adding Virtual Chassis #10493

New Issue
Closed
opened 2025-12-29 21:32:13 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:32:13 +01:00
Owner
Copy Link

Originally created by @Blackwhite-Edward on GitHub (Nov 20, 2024).

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

4.1.6

Python Version

3.12

Steps to Reproduce

image
An exception occurred when I added multiple members to the virtual cluster
One member is located in 38U of cabinet N02, and the other member is located in 38U of cabinet N03. However, when I was adding members, a message was displayed indicating that the two members cannot enter 38U at the same time. I understand that the virtual cluster can distinguish devices in different cabinets.

Expected Behavior

An exception occurred when I added multiple members to the virtual cluster
One member is located in 38U of cabinet N02, and the other member is located in 38U of cabinet N03. However, when I was adding members, a message was displayed indicating that the two members cannot enter 38U at the same time. I understand that the virtual cluster can distinguish devices in different cabinets.

Observed Behavior

Errors
Position
A virtual chassis member already exists in position 38.

Originally created by @Blackwhite-Edward on GitHub (Nov 20, 2024). ### Deployment Type Self-hosted ### Triage priority N/A ### NetBox Version 4.1.6 ### Python Version 3.12 ### Steps to Reproduce ![image](https://github.com/user-attachments/assets/bb7b7a4c-71e0-43f7-a022-e09f3a142a24) An exception occurred when I added multiple members to the virtual cluster One member is located in 38U of cabinet N02, and the other member is located in 38U of cabinet N03. However, when I was adding members, a message was displayed indicating that the two members cannot enter 38U at the same time. I understand that the virtual cluster can distinguish devices in different cabinets. ### Expected Behavior An exception occurred when I added multiple members to the virtual cluster One member is located in 38U of cabinet N02, and the other member is located in 38U of cabinet N03. However, when I was adding members, a message was displayed indicating that the two members cannot enter 38U at the same time. I understand that the virtual cluster can distinguish devices in different cabinets. ### Observed Behavior Errors Position A virtual chassis member already exists in position 38.
adam closed this issue 2025-12-29 21:32:13 +01:00
adam commented 2025-12-29 21:32:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 20, 2024):

The position field is the member's logical position within the virtual chassis, not it's physical position in a rack. The VC position is administratively assigned and must be unique for each member.

@jeremystretch commented on GitHub (Nov 20, 2024): The position field is the member's logical position within the virtual chassis, not it's physical position in a rack. The VC position is administratively assigned and must be unique for each member.
adam commented 2025-12-29 21:32:14 +01:00
Author
Owner
Copy Link

@Blackwhite-Edward commented on GitHub (Nov 21, 2024):

Tks.

@Blackwhite-Edward commented on GitHub (Nov 21, 2024): Tks.
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#10493
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?