Bug 1936430 - Auto_pinning Next Run configuration changes are cancelled after VM re-start.
Summary: Auto_pinning Next Run configuration changes are cancelled after VM re-start.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.5.6
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ovirt-4.5.0
: 4.5.0
Assignee: Liran Rotenberg
QA Contact: Polina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-08 13:35 UTC by Polina
Modified: 2022-04-20 06:33 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-4.5.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-20 06:33:59 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.5?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 118064 0 master MERGED backend: next-run numa update optional 2022-01-17 10:24:16 UTC

Comment 2 Polina 2022-04-18 14:21:57 UTC 
verified on ovirt-engine-4.5.0.2-0.7.el8ev.noarch

with VM updated APi , since the described request is not relevant for 4.5.

PUT https://{{host}}/ovirt-engine/api/vms/{{vm_id}}
<vm>
    <cpu>
        <topology>
            <sockets>1</sockets>
            <cores>1</cores>
            <threads>1</threads>
        </topology>
    </cpu>
    <cpu_pinning_policy>resize_and_pin_numa</cpu_pinning_policy>
</vm>

the VM is set with next run configuration and iit is applied after the restart
Comment 3 Sandro Bonazzola 2022-04-20 06:33:59 UTC 
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.