Bug 2009124

Added Marek to CC for Win10 awareness/help

> 3. Select and run tpm test case 

Since there are many, which test case was selected?

I tried to recreate the issue and could not.

(In reply to Stefan Berger from comment #2)
> > 3. Select and run tpm test case 
> 
> Since there are many, which test case was selected?

Hi Stefan,

This test is a sub test of TPM 2.0 - Functional 

Thanks,

Qinghua

> This test is a sub test of TPM 2.0 - Functional 

I couldn't recreate the issue.

   Stefan

Setting ITR just to ensure this reaches the radar during the release so that we can either resolve or close.

The latest test result:

rhel 9.1 

kernel: 5.14.0-156.el9.x86_64
qemu-kvm: qemu-kvm-7.1.0-1.el9.x86_64

swtpm-0.7.0-2.20211109gitb79fd91.el9.x86_64
libtpms-0.9.1-2.20211126git1ff6fe1f43.el9.x86_64
edk2-ovmf-20220526git16779ede2d36-3.el9.noarch

Get following failed test cases:
'Task error message : Test name: TPM - Auxiliary Test, Task name: Run Test, Cause : Task "Run Test" is Marked Failed From the LogFile', 
'Task error message : Test name: TPM 2.0 - Cryptographic Operations and RNG, Task name: Run Test, Cause : Task "Run Test" is Marked Failed From the LogFile', 
'Task error message : Test name: TPM 2.0 - Functional, Task name: Run Test, Cause : Task "Run Test" is Marked Failed From the LogFile', 
'Task error message : Test name: TPM 2.0 - NV Storage, Policy, Error Handling and Attestation, Task name: Run Test, Cause : Task "Run Test" is Marked Failed From the LogFile', 
'Task error message : Test name: TPM 2.0 - Stress, Task name: Run Test, Cause : Task "Run Test" is Marked Failed From the LogFile', 
'Task error message : Test name: TPM 2.0 EK Certificate Tests, Task name: Run Test, Cause : Task "Run Test" is Marked Failed From the LogFile'

I upload the WttEa.log for Functional test in the attachment for reference.

summary: 
 - Upgrading to libtpms v0.9.5 resolved the original issue of this BZ that I could previously not recreate but could recreate this time.  
 - I could not recreate any new issues as shown in comment #9.
 - Issues of 2 test cases are known and cannot be resolved.


I ran the tests now also again on

Fedora 36 host  with

swtpm 0.7.4      from git repo    [swtpm version is unlikely to be relevant in the test results here]
libtpms-0.9.1    from git repo
openssl-3.0.5-1.fc36.x86_64

The following were the results:

  -  Test name: TPM 2.0 - Cryptographic Operations and RNG
    => the original issue of this BZ could be recreated with libtpms 0.9.1 and disappeared with libtpms v0.9.5

  - Test name: TPM - Auxiliary Test   and
    Test name: TPM 2.0 EK Certificate Test
    => The errors that appeared here during my testing are known and documented in the 2nd table at the following link and cannot be resolved: https://github.com/stefanberger/libtpms/wiki/Testing-of-libtpms-Functionality#windows-hardware-lab-kit-tests

  - Test name: TPM 2.0 - Functional, Task name     and
    Test name: TPM 2.0 - NV Storage, Policy, Error Handling and Attestation    and
    Test name: TPM 2.0 - Stress

    => No error appeared with either libtpms v0.9.1 or libtpms v0.9.5

(In reply to Stefan Berger from comment #10)
> summary: 
>  - Upgrading to libtpms v0.9.5 resolved the original issue of this BZ that I
> could previously not recreate but could recreate this time.  

The LibTester.LibTesterTBSFunctional.WHCKTpmTbsAdminEncryptDecrypt test?

Do you know what broke the test and what fixed it?

thanks

Hi Stefan,

Thanks for recreating the bug again. I will try 0.9.5 when I get the downstream build.

Thanks,
Qinghua

(In reply to Stefan Berger from comment #10)
> summary: 
>  - Upgrading to libtpms v0.9.5 resolved the original issue of this BZ that I
> could previously not recreate but could recreate this time.  
>  - I could not recreate any new issues as shown in comment #9.
>  - Issues of 2 test cases are known and cannot be resolved.
> 
> 
> I ran the tests now also again on
> 
> Fedora 36 host  with
> 
> swtpm 0.7.4      from git repo    [swtpm version is unlikely to be relevant
> in the test results here]
> libtpms-0.9.1    from git repo
> openssl-3.0.5-1.fc36.x86_64
> 
> The following were the results:
> 
>   -  Test name: TPM 2.0 - Cryptographic Operations and RNG
>     => the original issue of this BZ could be recreated with libtpms 0.9.1
> and disappeared with libtpms v0.9.5
> 
>   - Test name: TPM - Auxiliary Test   and
>     Test name: TPM 2.0 EK Certificate Test
>     => The errors that appeared here during my testing are known and
> documented in the 2nd table at the following link and cannot be resolved:
> https://github.com/stefanberger/libtpms/wiki/Testing-of-libtpms-
> Functionality#windows-hardware-lab-kit-tests
> 
>   - Test name: TPM 2.0 - Functional, Task name     and
>     Test name: TPM 2.0 - NV Storage, Policy, Error Handling and Attestation 
> and
>     Test name: TPM 2.0 - Stress
> 
>     => No error appeared with either libtpms v0.9.1 or libtpms v0.9.5

(In reply to Marc-Andre Lureau from comment #11)
> (In reply to Stefan Berger from comment #10)
> > summary: 
> >  - Upgrading to libtpms v0.9.5 resolved the original issue of this BZ that I
> > could previously not recreate but could recreate this time.  
> 
> The LibTester.LibTesterTBSFunctional.WHCKTpmTbsAdminEncryptDecrypt test?

Yes.

> 
> Do you know what broke the test and what fixed it?

My guess would be that this patch here fixed it: https://github.com/stefanberger/libtpms/commit/1de757972e97dea11502c124fba3a64743d18df1

(In reply to Stefan Berger from comment #13)
> > Do you know what broke the test and what fixed it?
> 
> My guess would be that this patch here fixed it:
> https://github.com/stefanberger/libtpms/commit/
> 1de757972e97dea11502c124fba3a64743d18df1

That is fixed with https://bugzilla.redhat.com/show_bug.cgi?id=2093651.

@qcheng, could you check with >= libtpms-0.9.1-1.20211126git1ff6fe1f43.el9 ?

thanks

I get the same results as comment 9 with libtpms-0.9.1-1.20211126git1ff6fe1f43.el9.x86_64.

kernel: 5.14.0-160.el9.x86_64
qemu-kvm: qemu-kvm-7.1.0-1.el9.x86_64
libtpms: libtpms-0.9.1-1.20211126git1ff6fe1f43.el9.x86_64
openssl: openssl-3.0.1-41.el9_0.x86_64

Upload the WttEa.log file for Functional tests for your reference.

Hi @qcheng, could you try with 0.9.5 ? https://centos.softwarefactory-project.io/logs/9/9/95eea4b36f0d2e46f1ab439b5426b3dee6a4edbc/check/mock-build/d1ff91d/repo/

thanks

I got same results: 

'Task error message : Test name: TPM - Auxiliary Test, Task name: Run Test, Cause : Task "Run Test" is Marked Failed From the LogFile', 
'Task error message : Test name: TPM 2.0 - Cryptographic Operations and RNG, Task name: Run Test, Cause : Task "Run Test" is Marked Failed From the LogFile', 
'Task error message : Test name: TPM 2.0 - Functional, Task name: Run Test, Cause : Task "Run Test" is Marked Failed From the LogFile', 
'Task error message : Test name: TPM 2.0 - NV Storage, Policy, Error Handling and Attestation, Task name: Run Test, Cause : Task "Run Test" is Marked Failed From the LogFile', 
'Task error message : Test name: TPM 2.0 - Stress, Task name: Run Test, Cause : Task "Run Test" is Marked Failed From the LogFile', 
'Task error message : Test name: TPM 2.0 EK Certificate Tests, Task name: Run Test, Cause : Task "Run Test" is Marked Failed From the LogFile'

krnel: 5.14.0-210.el9.x86_64
qemu-kvm: qemu-kvm-7.1.0-6.el9.x86_64
swtpm-0.7.0-3.20211109gitb79fd91.el9.x86_64
libtpms-0.9.5-1.el9.x86_64
openssl-3.0.7-2.el9.x86_64
edk2-ovmf-20220826gitba0e0e4c6a-2.el9.noarch

I upload the WttEa.log for Cryptographic Operations and RNG in the attachment.

I don't really understand the failing test from the log. It seems to start with:
3324 7984 2022:12:12 2:41:39:892 Error: 0x8201aaac, Error 0x8201aaac   (Error ( status = 43692 ) in call: FindFileAndCopy( lpszFileName, lpszDestinationDir, 0, &dwFilesCopied, filecopyinfoDic) )   File=sdktools\dtm\wttbuild\coresys\client\executiontask\executiontask.cpp Line=2065    

Which doesn't look TPM related.

Furthermore, it's a bit weird that there are several "Build No Greater than 4000. This is a Windows Vista Machine    ". Perhaps you could share the details of your WHLK setup.

Hi Marc-Andre,

My Win10 guest is installed from our internal iso and checked inside the guest:

Edition Windows 10 Enterprise
Version 21H2

HLK is 2004

If you need more information, please let me know.

Thanks,
Qinghua

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.

Let's open this bz for more investigation.

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.