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

VM site not updated when changing cluster site #15020

Closed
jeremystretch opened this issue Feb 2, 2024 · 0 comments · Fixed by #15031
Closed

VM site not updated when changing cluster site #15020

jeremystretch opened this issue Feb 2, 2024 · 0 comments · Fixed by #15031
Assignees
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@jeremystretch
Copy link
Member

Deployment Type

NetBox Cloud

NetBox Version

v3.7.1

Python Version

3.11

Steps to Reproduce

  1. Create two sites, Site A and Site B.
  2. Create a new virtualization cluster (of any type) and assign it to Site A.
  3. Create a new virtual machine in the cluster. Do not assign a site when creating the VM.
  4. Verify that the new VM is assigned to Site A.
  5. Edit the cluster and change its site to Site B.
  6. Check the VM's assigned site.

Expected Behavior

The VM's site should be updated to Site B.

Observed Behavior

The VM is still assigned to Site A, whereas its cluster is assigned to Site B.

When attempting to save the VM, validation fails, complaining that its site and its cluster's site do not match.

@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application 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 labels Feb 2, 2024
@arthanson arthanson self-assigned this Feb 2, 2024
@arthanson arthanson removed the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Feb 2, 2024
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Feb 2, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants