Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1936430

Summary: Auto_pinning Next Run configuration changes are cancelled after VM re-start.
Product: [oVirt] ovirt-engine Reporter: Polina <pagranat>
Component: BLL.VirtAssignee: Liran Rotenberg <lrotenbe>
Status: CLOSED CURRENTRELEASE QA Contact: Polina <pagranat>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4.5.6CC: ahadas, bugs
Target Milestone: ovirt-4.5.0Flags: pm-rhel: ovirt-4.5?
Target Release: 4.5.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.5.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-20 06:33:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.