starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

An identical virtual-cluster name in different sites #1618

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

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

Issue type

[] Feature request
[X] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: v2.3.1

Description

Seemingly, there is no way to have an identical virtual-cluster name in different sites.

How to reproduce the error:

  1. Go to virtualization > clusters
  2. push "Add" button
  3. Create a new cluster under name "test" located in site "testlocation1"
  4. Repeat step #1 and Return user to previous query after performing a bulk action (#2)
  5. Create a new cluster under name "test" located in site "testlocation2"

In this use case, the following error comes up:
Cluster with this Name already exists.

Originally created by @mabazyar on GitHub (Mar 9, 2018). ### Issue type [] Feature request [X] Bug report [ ] Documentation ### Environment * Python version: 3.5.2 * NetBox version: v2.3.1 ### Description Seemingly, there is no way to have an identical virtual-cluster name in different sites. How to reproduce the error: 1) Go to virtualization > clusters 2) push "Add" button 3) Create a new cluster under name "test" located in site "testlocation1" 4) Repeat step #1 and #2 5) Create a new cluster under name "test" located in site "testlocation2" In this use case, the following error comes up: Cluster with this Name already exists.
adam added the status: acceptedtype: feature labels 2025-12-29 16:33:32 +01:00
adam closed this issue 2025-12-29 16:33:32 +01:00
adam commented 2025-12-29 16:33:33 +01:00
Author
Owner
Copy Link

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

There's a strong parallel between this and #238, which addresses a similar restriction on racks/groups.

@jeremystretch commented on GitHub (Mar 9, 2018): There's a strong parallel between this and #238, which addresses a similar restriction on racks/groups.
adam commented 2025-12-29 16:33:33 +01:00
Author
Owner
Copy Link

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

Folding this into #1943

@jeremystretch commented on GitHub (Mar 14, 2018): Folding this into #1943
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: feature
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#1618
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?