Created attachment 1698075 [details] screenshot of the CPU pinning / CPU affinity in the API
Created attachment 1698076 [details] screenshot of CPU pinning / CPU affinity in the webadmin
Created attachment 1698080 [details] screenshot of CPU pinning / CPU affinity in the webadmin
https://github.com/ManageIQ/manageiq-providers-ovirt/pull/502
The "vcpu" property is the VMs CPU number. The "cpu_set" is the Hypervisors CPU number. Both need to be collected and displayed in relation to each other. Currently it looks like only the "vcpu" property is being collected in a comma seperated list?
https://github.com/ManageIQ/manageiq-providers-ovirt/pull/503
New commits detected on ManageIQ/manageiq-providers-ovirt/ivanchuk: https://github.com/ManageIQ/manageiq-providers-ovirt/commit/4e2b450443866fdd2bee8aef55ac596374b3e041 commit 4e2b450443866fdd2bee8aef55ac596374b3e041 Author: Adam Grare <agrare> AuthorDate: Fri Jun 19 16:57:10 2020 +0000 Commit: Satoe Imaishi <simaishi> CommitDate: Wed Aug 19 15:48:21 2020 +0000 Merge pull request #502 from djberg96/cpu_affinity Add cpu_affinity for vms (cherry picked from commit 81b4613cb4f9c9f42b38f69feca2fe68044a35c4) https://bugzilla.redhat.com/show_bug.cgi?id=1846623 app/models/manageiq/providers/redhat/inventory/parser/infra_manager.rb | 4 +- 1 file changed, 3 insertions(+), 1 deletion(-) https://github.com/ManageIQ/manageiq-providers-ovirt/commit/327e8f5579f7c4bfb68be8e549ff6b47d5b499f3 commit 327e8f5579f7c4bfb68be8e549ff6b47d5b499f3 Author: Adam Grare <agrare> AuthorDate: Mon Jun 22 18:33:43 2020 +0000 Commit: Satoe Imaishi <simaishi> CommitDate: Wed Aug 19 15:48:52 2020 +0000 Merge pull request #503 from djberg96/cpu_affinity Update cpu affinity to include both virtual and host cpu (cherry picked from commit 4bb2e0fbf37e65ea96ba69b87bc94b7814d3d9c5) https://bugzilla.redhat.com/show_bug.cgi?id=1846623 app/models/manageiq/providers/redhat/inventory/parser/infra_manager.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Verified on 5.11.8.0.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: CloudForms 5.0.8 security, bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:4134