Bug 2010215

Summary:	RFE: vTPM tests with HCK-CI
Product:	Red Hat Enterprise Linux 9	Reporter:	Marc-Andre Lureau <marcandre.lureau>
Component:	virtio-win	Assignee:	Yvugenfi <yvugenfi>
virtio-win sub component:	others	QA Contact:	Qianqian Zhu <qizhu>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	coli, jferlan, jinzhao, juzhang, lijin, qcheng, qizhu
Version:	unspecified	Keywords:	FutureFeature, Reopened, TestOnly
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
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:45:57 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marc-Andre Lureau 2021-10-04 08:30:40 UTC

The vTPM developpers and QA are regularly testing regressions with HLK. Setting up the VMs and configuration is manual, a bit tedious and error prone.

After hearing from HCK-CI during KVM Forum, I imagine it could be useful to automate the testing of vTPM.

Upstream should provide options to test both TPM TIS and CRB devices, 1.2 or 2.0 version, BIOS or UEFI, and a location for the TPM state (so it can be prepared with swtpm-setup before the test, for example). Ideally, CI integration should be added to libtpms github project (and if possible Fedora gating).

In the context of RHEL, we only support UEFI+CRB+2.0 for x86. We should also work on adding gating support eventually.

thanks

Comment 2 CongLi 2022-01-05 08:30:13 UTC


*** This bug has been marked as a duplicate of bug 2007121 ***

Comment 3 Yvugenfi@redhat.com 2022-01-05 09:23:44 UTC

This is not the same as BZ#2007121

* Current bug is about adding vTPM support

* BZ#2007121 is about automating the deployment of HCK-CI on test servers

Comment 8 errata-xmlrpc 2022-11-15 10:45:57 UTC

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