Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1886380

Summary: tpm2-abrmd won't start from Beaker because of EPERM on /dev/tpm0
Product: Red Hat Enterprise Linux 8 Reporter: Vilém Maršík <vmarsik>
Component: tpm2-abrmdAssignee: Štěpán Horáček <shoracek>
Status: CLOSED WONTFIX QA Contact: Vilém Maršík <vmarsik>
Severity: low Docs Contact:
Priority: unspecified    
Version: 8.3CC: bhu, core-kernel-mgr, jdluhos, jsnitsel, skozina
Target Milestone: rcKeywords: Triaged
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-08 07:27:23 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:

Comment 1 Jerry Snitselaar 2020-11-17 21:58:46 UTC
Any chance I can get access to this system? The lenovo-sr650 I just looked at has a tpm1.2 device.

Comment 2 Jerry Snitselaar 2020-11-17 22:36:04 UTC
Does the rlRun "udevadm trigger --action=change" wait for the udevadm command to complete before the next thing happens? Since it is complaining about permissions, I'm wondering if the udev rule hasn't kicked in yet. Maybe try a sleep after the rlRun?
Also should there be a 'systemctl enable tpm2-abrmd' somewhere before the systemctl start tpm2-abrmd to set up the symlink?

Comment 3 Jerry Snitselaar 2020-11-17 23:30:07 UTC
I guess a systemctl enable isn't needed.

Has this been encountered on any system besides the Lenovo? Are you able to log into the system after the test has run? It would be interesting to see what the permissions are on /dev/tpm0.

Doesn't look like it is necessary right now, but you can read specific banks and registers with the tpm2_pcrread command, so tpm2_pcrread -T tabrmd sha1:4 would just return register 4 from the sha1 bank. I know some systems report multiple banks, and I believe we have a Dell somewhere where you can flip between sha1 and sha256. We might need to get more complicated at some point and look at 'tpm2_getcap pcrs' to see what banks are available on the system, and then use that to decide what to read and extend.

Comment 4 Vilém Maršík 2020-11-24 15:48:05 UTC
Jerry, do you want me to reserve the machine for you? I though you try a Loan request.

Comment 5 Jerry Snitselaar 2020-11-24 18:07:35 UTC
Are you able to try the test with a sleep in between the udevadm trigger call and the systemctl start?

Comment 8 RHEL Program Management 2022-04-08 07:27:23 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.