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 device names based on cluster. #8978

New Issue
Closed
opened 2025-12-29 20:43:35 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:43:35 +01:00
Owner
Copy Link

Originally created by @emersonfelipesp on GitHub (Dec 16, 2023).

NetBox version

v3.6.7

Feature type

Change to existing functionality

Proposed functionality

Currently device names can be duplicated if its on different Site or Tenants. I would like to propose the same "allow duplicate" behavior, but based on the Cluster field only (not needing to fill Site or Tenants field).

Use case

Lets consider this scenario:

netbox_duplicate_device_names drawio

On my hypervisor, I have different Clusters that shares the same Nodes names as described on the image, but both clusters resides on the same physical site building. (I separated it on different racks just to illustrate)

My current workaround is to add "fictional" site like this:

Site Cluster Device
Site A Cluster A Node A
Site B Cluster B Node A
  • The Site B was created just to allow duplicated device names

But on on my scenario, the solution should be:

Site Cluster Device
Building A Cluster A Node A
Building A Cluster B Node A
  • Where the differentiation to allow duplicate device name is now based on the Cluster, not the Site.

Database changes

No response

External dependencies

No response

Originally created by @emersonfelipesp on GitHub (Dec 16, 2023). ### NetBox version v3.6.7 ### Feature type Change to existing functionality ### Proposed functionality Currently device names can be duplicated if its on different **Site** or **Tenants**. I would like to propose the same "allow duplicate" behavior, but based on the **Cluster** field only (not needing to fill Site or Tenants field). ### Use case ### Lets consider this scenario: ![netbox_duplicate_device_names drawio](https://github.com/netbox-community/netbox/assets/24397251/0048794c-2862-4c66-a2d4-e95090779b23) On my hypervisor, I have different Clusters that shares the same Nodes names as described on the image, but **both clusters resides on the same physical site building.** (I separated it on different racks just to illustrate) ### My current workaround is to add "fictional" site like this: | Site | Cluster | Device | |-----|---------|---------| | Site A | Cluster A | Node A | | Site B | Cluster B | Node A | - The **Site B** was created just to allow **duplicated device names** ### But on on my scenario, the solution should be: | Site | Cluster | Device | |-----|---------|---------| | Building A | Cluster A | Node A | | Building A | Cluster B | Node A | - Where the differentiation to allow duplicate device name is now based on the Cluster, not the Site. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:43:35 +01:00
adam closed this issue 2025-12-29 20:43:35 +01:00
adam commented 2025-12-29 20:43:36 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 16, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 16, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:43:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 27, 2024):

I'm going to decline this change as the designation of a device as a cluster host should not be considered as part of its identifier. (There's also no justification offered above for having duplicate device names within the same site.)

@jeremystretch commented on GitHub (Mar 27, 2024): I'm going to decline this change as the designation of a device as a cluster host should not be considered as part of its identifier. (There's also no justification offered above for having duplicate device names within the same site.)
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: 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#8978
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?