Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 2017541

Summary:	systemd - tpm2 is missing
Product:	Red Hat Enterprise Linux 9	Reporter:	lejeczek <peljasz>
Component:	systemd	Assignee:	David Tardon <dtardon>
Status:	CLOSED ERRATA	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, dtardon, jamacku, jwboyer, riehecky, systemd-maint-list
Target Milestone:	rc	Keywords:	Reproducer, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	systemd-250-3.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-17 15:57:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description lejeczek 2021-10-26 18:52:38 UTC

Description of problem:

-> $ systemd-cryptenroll --tpm2-device=list
TPM2 not supported on this build. 

Version-Release number of selected component (if applicable):

systemd-249-4.el9.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 David Tardon 2021-11-05 09:51:16 UTC

I don't remember any talks about disabling TPM2 support, therefore I think we just haven't noticed it's auto-disabled because its build deps are missing...

Comment 5 errata-xmlrpc 2022-05-17 15:57:34 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 (new packages: systemd), 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:3979