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

Issue creating virtual-machine with only cluster field filled in #6867

New Issue
Closed
opened 2025-12-29 19:46:11 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:46:11 +01:00
Owner
Copy Link

Originally created by @joeribloemen on GitHub (Aug 24, 2022).

NetBox version

v3.3.0

Python version

3.10

Steps to Reproduce

  1. Go to virtual-machines tab under Virtualization
  2. Click add virtual machine
  3. Fill in name and cluster
  4. Click create and recieve error: the selected cluster (**** is not assigned to this site (None).)

Expected Behavior

In the patch notes it stands that either site or/and cluster need to be assigned to the virtual machine.

image

I expected if the site field is not filled in, the site field is just inherted from the cluster object.

Is this behavior normal ?

Observed Behavior

Error
image

Originally created by @joeribloemen on GitHub (Aug 24, 2022). ### NetBox version v3.3.0 ### Python version 3.10 ### Steps to Reproduce 1. Go to virtual-machines tab under Virtualization 2. Click add virtual machine 3. Fill in name and cluster 4. Click create and recieve error: the selected cluster (**** is not assigned to this site (None).) ### Expected Behavior In the patch notes it stands that either site or/and cluster need to be assigned to the virtual machine. ![image](https://user-images.githubusercontent.com/18398257/186421055-11370080-365a-4a37-90be-38a6327c75ff.png) I expected if the site field is not filled in, the site field is just inherted from the cluster object. Is this behavior normal ? ### Observed Behavior Error ![image](https://user-images.githubusercontent.com/18398257/186422217-2720ac00-74db-4743-8455-5b6281def5fc.png)
adam added the type: bug label 2025-12-29 19:46:11 +01:00
adam closed this issue 2025-12-29 19:46:12 +01:00
adam commented 2025-12-29 19:46:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 24, 2022):

You've skipped the part where you create the cluster. If the cluster to which you're assigning the VM is associated with a site, then this is expected: Both the VM and its cluster must belong to the same site, or to no site.

I can confirm that creating a new cluster with no site assigned, and then creating a new VM assigned to that cluster works as expected on v3.3.0.

@jeremystretch commented on GitHub (Aug 24, 2022): You've skipped the part where you create the cluster. If the cluster to which you're assigning the VM is associated with a site, then this is expected: Both the VM and its cluster must belong to the same site, or to no site. I can confirm that creating a new cluster with no site assigned, and then creating a new VM assigned to that cluster works as expected on v3.3.0.
adam commented 2025-12-29 19:46:13 +01:00
Author
Owner
Copy Link

@joeribloemen commented on GitHub (Aug 24, 2022):

Okey, Thanks for the explanation.

Have a great day!

@joeribloemen commented on GitHub (Aug 24, 2022): Okey, Thanks for the explanation. Have a great day!
adam commented 2025-12-29 19:46:13 +01:00
Author
Owner
Copy Link

@bb-Ricardo commented on GitHub (Aug 29, 2022):

Hey, just wondering. If the site is enforced by the cluster, and NetBox is aware of the cluster site, then why do I need to specify a site for the VM if the VM will be assigned to a cluster?

@bb-Ricardo commented on GitHub (Aug 29, 2022): Hey, just wondering. If the site is enforced by the cluster, and NetBox is aware of the cluster site, then why do I need to specify a site for the VM if the VM will be assigned to a cluster?
adam commented 2025-12-29 19:46:13 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 29, 2022):

VMs can also be assigned to a site without specifying a cluster, so an explicit entry is necessary for validation.

@jeremystretch commented on GitHub (Aug 29, 2022): VMs can also be assigned to a site without specifying a cluster, so an explicit entry is necessary for validation.
adam commented 2025-12-29 19:46:13 +01:00
Author
Owner
Copy Link

@bb-Ricardo commented on GitHub (Aug 29, 2022):

That is a great feature, but then the site and cluster attribute should be mutually exclusive. You either select a site OR a cluster as the cluster enforces the site attribute. This is also stated in the release notes (see issue description)

@bb-Ricardo commented on GitHub (Aug 29, 2022): That is a great feature, but then the site and cluster attribute should be mutually exclusive. You either select a site OR a cluster as the cluster enforces the site attribute. This is also stated in the release notes (see issue description)
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: bug
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#6867
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?