Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Virtualization: Modifying a cluster field also modifies member virtual machine sites #18553

Open
cruse1977 opened this issue Jan 31, 2025 · 0 comments
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@cruse1977
Copy link
Member

Deployment Type

NetBox Cloud

NetBox Version

v4.2.2

Python Version

3.12

Steps to Reproduce

  1. Create a cluster with a blank scope
  2. Create some VM's, assign them to the cluster and assign them to a site
  3. Edit a field on the cluster (eg description) and save

Expected Behavior

Virtual Machines are not modified.

Observed Behavior

Virtual Machine site fields are cleared to match the cluster scope.

Note - there is some validation in netbox whereas a cluster is scoped to a site, you cannot add vms within a different site. This is expected given the cluster as been explicitly scoped.

However, modifying a field in the cluster should not impact virtual machines.

One big use case for this functionality is if the cluster is not scoped to a specific site - for example in an overlay cluster spanning multiple sites in which case virtual machines within a single cluster may be in multiple sites.

@cruse1977 cruse1977 added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Jan 31, 2025
@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: medium Results in substantial degraded or broken functionality for specfic workflows and removed status: needs triage This issue is awaiting triage by a maintainer labels Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants