Created attachment 1895140 [details] engine log Description of problem: sometimes happen after deployment of the environment. I such a case no dedicated VM could start . engine restart is required first Version-Release number of selected component (if applicable): ovirt-engine-4.5.1.2-0.11.el8ev.noarch How reproducible: a lot after new deployment of environment Steps to Reproduce: 1. deploy environment 2. run dedicated VM with 1 CPU Actual results: an attempt to start a dedicated VM with 1 CPU brings error "2022-07-05 13:38:07,639+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-5) [38b10ae0-66ef-4c89-b4f3-a56ae1df2c60] EVENT_ID: USER_FAILED_RUN_VM(54), Failed to run VM golden_env_mixed_virtio_1_0 due to a failed validation: [Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:, The host host_mixed_1 did not satisfy internal filter CpuPinning because the CPU topology of the host has not been retrieved.., The host host_mixed_1 did not satisfy internal filter CpuPinning because the CPU topology of the host has not been retrieved.., The host host_mixed_1 did not satisfy internal filter CpuPinning because the CPU topology of the host has not been retrieved..] Expected results: VM must run Additional info:
the bug is on_qa , but still happens on the last available build . tested on ovirt-engine-4.5.2-0.3.el8ev.noarch
Verified with: ovirt-engine-4.5.2.1-0.1.el8ev.noarch Steps: The same steps as in the bug description(used GE-3) Results: The VM runs successfully.
This bugzilla is included in oVirt 4.5.2 release, published on August 10th 2022. Since the problem described in this bug report should be resolved in oVirt 4.5.2 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.