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

engine: Save updated Numa Nodes into NEXT_RUN snapshot #498

Merged
merged 1 commit into from
Jun 29, 2022

Conversation

ljelinkova
Copy link
Contributor

When creating a VM configuration string from the VM object, the NUMA Node list was always updated from the database. This caused that the new settings for the VM were not saved into the NEXT_RUN snapshot.

Bug-Url: https://bugzilla.redhat.com/2099225

When creating a VM configuration string from the VM object,
the NUMA Node list was always updated from the database.
This caused that the new settings for the VM were not
saved into the NEXT_RUN snapshot.

Bug-Url: https://bugzilla.redhat.com/2099225
@ahadas
Copy link
Member

ahadas commented Jun 28, 2022

/ost

@ahadas ahadas merged commit 3f13de6 into oVirt:master Jun 29, 2022
@ljelinkova ljelinkova deleted the numa-next-run branch June 29, 2022 12:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants