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

Allow duplicate cluster names within a site #1597

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

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

Originally assigned to: @jeremystretch on GitHub.

Issue type

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

Environment

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

Description

There is no possibility to represent an infrastructure having two different virtual clusters with the same name in two different virtual cluster groups located in different Sites. Whereas, this possibility is in place in racks.

The following shows how to reproduce the issue:

  1. Hit "Cluster-Groups" under virtualization menu
  2. Add two different cluster groups like cg1 and cg2
  3. Hit "Clusters" under virtualization menu
  4. add a cluster and name it like "staging" and put it under cg1
  5. add one more cluster with the same name and put it under cg2

At step 5, you will encounter error "Cluster with this Name already exists".

Originally created by @mabazyar on GitHub (Mar 2, 2018). Originally assigned to: @jeremystretch on GitHub. ### Issue type [] Feature request [X] Bug report [ ] Documentation ### Environment * Python version: 3.5.2 * NetBox version: v2.3.0 ### Description There is no possibility to represent an infrastructure having two different virtual clusters with the same name in two different virtual cluster groups located in different Sites. Whereas, this possibility is in place in racks. The following shows how to reproduce the issue: 1) Hit "Cluster-Groups" under virtualization menu 2) Add two different cluster groups like cg1 and cg2 3) Hit "Clusters" under virtualization menu 4) add a cluster and name it like "staging" and put it under cg1 5) add one more cluster with the same name and put it under cg2 At step 5, you will encounter error "Cluster with this Name already exists".
adam added the status: acceptedtype: feature labels 2025-12-29 16:33:19 +01:00
adam closed this issue 2025-12-29 16:33:19 +01:00
adam commented 2025-12-29 16:33:20 +01:00
Author
Owner
Copy Link

@mabazyar commented on GitHub (Mar 7, 2018):

Just wanted to follow up to make sure if it is doable.
Cheers,

@mabazyar commented on GitHub (Mar 7, 2018): Just wanted to follow up to make sure if it is doable. Cheers,
adam commented 2025-12-29 16:33:20 +01:00
Author
Owner
Copy Link

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

@jeremystretch

I think it may have to do with
https://github.com/digitalocean/netbox/issues/238
and
https://github.com/digitalocean/netbox/issues/1963

@mabazyar commented on GitHub (Mar 9, 2018): @jeremystretch I think it may have to do with https://github.com/digitalocean/netbox/issues/238 and https://github.com/digitalocean/netbox/issues/1963
adam commented 2025-12-29 16:33:20 +01:00
Author
Owner
Copy Link

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

This pretty much parallels #238, which would allow duplicate rack names within a site.

@jeremystretch commented on GitHub (Mar 14, 2018): This pretty much parallels #238, which would allow duplicate rack names within a site.
adam commented 2025-12-29 16:33:21 +01:00
Author
Owner
Copy Link

@Simperdy commented on GitHub (Feb 5, 2021):

I have the same problem. This would be very useful for me.

@Simperdy commented on GitHub (Feb 5, 2021): I have the same problem. This would be very useful for me.
adam commented 2025-12-29 16:33:21 +01:00
Author
Owner
Copy Link

@SquirrelSloth commented on GitHub (Mar 11, 2021):

Same as Simperdy and bb-Ricardo, we have 9 vCenter instances running in 3 environments and several of them have the same cluster names, but even though they are from different cluster groups we cannot create the duplicate clusters, leaving us to either group them all together or append the environment to the cluster name (which is not optimal because it doesn't reflect the actual cluster name in vCenter).
Being able to keep the naming constraint just within a cluster group is fine (like how setting IP address unique enforcement within a specific VRF is done right now).

@SquirrelSloth commented on GitHub (Mar 11, 2021): Same as Simperdy and bb-Ricardo, we have 9 vCenter instances running in 3 environments and several of them have the same cluster names, but even though they are from different cluster groups we cannot create the duplicate clusters, leaving us to either group them all together or append the environment to the cluster name (which is not optimal because it doesn't reflect the actual cluster name in vCenter). Being able to keep the naming constraint just within a cluster group is fine (like how setting IP address unique enforcement within a specific VRF is done right now).
adam commented 2025-12-29 16:33:21 +01:00
Author
Owner
Copy Link

@WilliamDEdwards commented on GitHub (Apr 19, 2021):

+1. This would allow for administering multisite virtualisation clusters.

@WilliamDEdwards commented on GitHub (Apr 19, 2021): +1. This would allow for administering multisite virtualisation clusters.
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#1597
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?