Bug 2104858

Summary: CPU topology of the host has not been retrieved while first query VdsManager::initAvailableCpus()
Product: [oVirt] ovirt-engine Reporter: Polina <pagranat>
Component: BLL.VirtAssignee: Lucia Jelinkova <ljelinko>
Status: CLOSED CURRENTRELEASE QA Contact: Qin Yuan <qiyuan>
Severity: high Docs Contact:
Priority: medium    
Version: 4.5.1CC: ahadas, bugs, mavital, mperina, mzamazal
Target Milestone: ovirt-4.5.2Keywords: ZStream
Target Release: 4.5.2Flags: sbonazzo: ovirt-4.5+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.5.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-30 08:47:42 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:
Attachments:
Description Flags
engine log none

Description Polina 2022-07-07 10:35:44 UTC
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:

Comment 2 Polina 2022-08-02 18:53:22 UTC
the bug is on_qa , but still happens on the last available build . tested on ovirt-engine-4.5.2-0.3.el8ev.noarch

Comment 3 Qin Yuan 2022-08-08 15:23:44 UTC
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.

Comment 4 Sandro Bonazzola 2022-08-30 08:47:42 UTC
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.