Bug 2158597

Summary: cannot get EK certificate after updating to tpm2-tss-3.2.1-1
Product: [Fedora] Fedora Reporter: Karel Srot <ksrot>
Component: tpm2-tssAssignee: Peter Robinson <pbrobinson>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 36CC: fmartine, jsnitsel, pbrobinson, yunying.sun
Target Milestone: ---Keywords: Regression
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: 2023-01-06 03:30:24 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 Karel Srot 2023-01-05 19:12:07 UTC 
Description of problem:

After updating to tpm2-tss-3.2.1-1 one cannot get EK certificate

# tpm2_getekcertificate -o ek_ecc.crt
ERROR:esys:src/tss2-esys/esys_iutil.c:1096:esys_GetResourceObject() Error: Esys handle does not exist (70018). 
ERROR: Esys_SequenceComplete(0x70018) - esapi:The ESYS_TR resource object is bad
ERROR: Failed to get shandle
ERROR: Failed to read NVRAM area at index 0x1C00002

This is a regression compared to tpm2-tss-3.2.0-1.fc36.
Tested with swtpm

Version-Release number of selected component (if applicable):
tpm2-tss-3.2.1-1.f36
tpm2-tools-5.2-2.fc36

How reproducible:
always

Steps to Reproduce:
1. see above
Comment 1 Peter Robinson 2023-01-06 03:30:24 UTC 
There's really no need to file two identical bugs, once we have a fix it'll go to all current releases.

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