Bug 2170556

Summary: [SVVP] job 'Check SMBIOS Table Specific Requirements' failed on win2022 [rhel-9.3.0]
Product: Red Hat Enterprise Linux 9 Reporter: RHEL Program Management Team <pgm-rhel-tools>
Component: qemu-kvmAssignee: Julia Suvorova <jusual>
qemu-kvm sub component: Devices QA Contact: dehanmeng <demeng>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: medium    
Priority: high CC: coli, jinzhao, juzhang, mkedzier, mrezanin, qizhu, virt-maint, xuwei, ymankad
Version: 9.2Keywords: TestOnly, Triaged
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Windows   
Whiteboard:
Fixed In Version: qemu-kvm-8.0.0-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2169904 Environment:
Last Closed: 2023-09-13 07:28:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2169904, 2180898    
Bug Blocks:    

Comment 1 John Ferlan 2023-02-22 12:05:51 UTC 
Since you now own the RHEL 9.2 bug 2169904, I'll assign to you.  Once the fix is upstream in qemu-8.0, then we can just move the bug along in the process by moving to POST with the commit id in the devel whiteboard and setting various flags.
Comment 2 Qianqian Zhu 2023-03-13 05:18:14 UTC 

*** This bug has been marked as a duplicate of bug 2169904 ***
Comment 5 dehanmeng 2023-04-13 01:49:45 UTC 
Currently, the qemu8.0 downstream is not ready, so for now, we can just keep ON_QA status until all is ready. Extend ITM to 10.
Comment 6 dehanmeng 2023-04-23 02:50:38 UTC 
After test svvp case "Check SMBIOS Table Specific Requirements" with the latest downstream qemu8.0 package. case has been passed. Move this bug status to VERIFIED. thanks.
Comment 9 RHEL Program Management 2023-09-13 07:28:43 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.