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

Virtual Machines with duplicate names displayed only once #7312

New Issue
Closed
opened 2025-12-29 20:21:40 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:21:40 +01:00
Owner
Copy Link

Originally created by @sincomil on GitHub (Dec 2, 2022).

NetBox version

v.3.3.9

Python version

3.9

Steps to Reproduce

  1. create virtual machine with name: foo in cluster: bar with active state
  2. create virtual machine with same name foo in cluster bar with offline sate
  3. got an error: A virtual machine with this name already exists in the assigned cluster.

Expected Behavior

VMs with a same names should have to exist in the same cluster, the unique identifiers for distinguishing VMs used in VMWare is VM UUIDs - so you users can have multiple VMs with a same names in single cluster/hypervisor node

Observed Behavior

error: A virtual machine with this name already exists in the assigned cluster.

Originally created by @sincomil on GitHub (Dec 2, 2022). ### NetBox version v.3.3.9 ### Python version 3.9 ### Steps to Reproduce 1. create virtual machine with name: `foo` in cluster: `bar` with `active` state 2. create virtual machine with same name foo in cluster bar with offline sate 3. got an error: _**A virtual machine with this name already exists in the assigned cluster.**_ ### Expected Behavior VMs with a same names should have to exist in the same cluster, the unique identifiers for distinguishing VMs used in VMWare is VM UUIDs - so you users can have multiple VMs with a same names in single cluster/hypervisor node ### Observed Behavior error: _**A virtual machine with this name already exists in the assigned cluster.**_
adam closed this issue 2025-12-29 20:21:40 +01:00
adam commented 2025-12-29 20:21:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 2, 2022):

The error message is correct: Each VM within a cluster must have a unique name. This has always been the case.

@jeremystretch commented on GitHub (Dec 2, 2022): The error message is correct: Each VM within a cluster must have a unique name. This has always been the case.
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#7312
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?