Bug 2082021
| Summary: | [virtio-win][vioscsi][viostor] Job "DF - Embedded Signature Verification Test" Failed with virtio-win-prewhql-218 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Peixiu Hou <phou> |
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> |
| virtio-win sub component: | virtio-win-prewhql | QA Contact: | Peixiu Hou <phou> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | urgent | CC: | coli, jinzhao, juzhang, menli, qizhu, vrozenfe, xiagao |
| Version: | 9.0 | Keywords: | Regression, Triaged |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Windows | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-15 10:46:41 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: | |||
|
Description
Peixiu Hou
2022-05-05 08:44:37 UTC
Hi Peixiu Can you please upload the HLK log file? Thanks, Vadim. Another question Can you please confirm that the test certificate was installed to the Trusted Root Certification Authorities certificate store and the Trusted Publishers certificate store before running the test? https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/install/installing-a-test-certificate-on-a-test-computer.md Thanks, Vadim. hit the same issue with viostor. Hi Vadim, I tested all guests for vioscsi with virtio-win-prewhql-221 build, all can be passed. Just there are some difference between different guests. Details as follows: 1) On win2022, win2019, win2016, we can pass the job without adding new cert file, run directly and then passed. checked the certmgr.msc found no original cert file show in root/trustedpublisher dir. 2) On win8.1-32/64, win10-32/64, win2012-64, win11-64, we passed this case need to aditional add new cert file, otherwise, the job cannot be passed. checked the certmgr.msc, also none original cert file show in root/trustedpublisher dir. 3) On win2012-r2, the certmgr.msc include an original cert file, delete it then add the new cert, passed this job. I wonder what's the reason for these different? and if possible they can be unified as 1) situation or be added with the driver installation automatically? And, this command "signtool verify /v /pa /c x:\builds\b221\bin\Win10\amd64\viostor.cat x:\builds\b221\bin\Win10\amd64\viostor.sys x:\builds\b221\bin\Win10\amd64\viostor.inf", only when we added the new cert file, it'll work yes? Thanks~ Peixiu (In reply to Peixiu Hou from comment #23) > Hi Vadim, > > I tested all guests for vioscsi with virtio-win-prewhql-221 build, all can > be passed. Just there are some difference between different guests. > > Details as follows: > 1) On win2022, win2019, win2016, we can pass the job without adding new cert > file, run directly and then passed. checked the certmgr.msc found no > original cert file show in root/trustedpublisher dir. > > 2) On win8.1-32/64, win10-32/64, win2012-64, win11-64, we passed this case > need to aditional add new cert file, otherwise, the job cannot be passed. > checked the certmgr.msc, also none original cert file show in > root/trustedpublisher dir. > > 3) On win2012-r2, the certmgr.msc include an original cert file, delete it > then add the new cert, passed this job. > > I wonder what's the reason for these different? and if possible they can be > unified as 1) situation or be added with the driver installation > automatically? > I wonder if all the guest were installed similarly, using the same procedure? > And, this command "signtool verify /v /pa /c > x:\builds\b221\bin\Win10\amd64\viostor.cat > x:\builds\b221\bin\Win10\amd64\viostor.sys > x:\builds\b221\bin\Win10\amd64\viostor.inf", only when we added the new cert > file, it'll work yes? > Yes we need the new cert to be added to the trustedpublisher repository. Otherwive the test will fail. Best regards, Vadim. > Thanks~ > Peixiu 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 (virtio-win 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/RHBA-2022:8261 |