action #107107
closed[Tumbleweed][security] test fails in tpm2_engine_rsa_operation
100%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-security_tpm2_swtpm@64bit fails in
tpm2_engine_rsa_operation
The test results 'incomplete' - in autoinst.txt I can find
[2022-02-18T21:34:45.050901Z] [warn] !!! : qemu-system-x86_64: -chardev socket,id=chrtpm,path=/tmp/mytpm1/swtpm-sock: Failed to connect to '/tmp/mytpm1/swtpm-sock': No such file or directory
Test suite description¶
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
Reproducible¶
Fails since (at least) Build 20220217 (current job)
Expected result¶
Last good: 20220216 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by dimstar almost 3 years ago
Re-ran last good release, which also fails, thus excluding a product change failure
Updated by llzhao over 2 years ago
- Subject changed from test fails in tpm2_engine_rsa_operation to [Tumbleweed][security] test fails in tpm2_engine_rsa_operation
- Assignee set to rfan1
- Estimated time set to 8.00 h
Updated by rfan1 over 2 years ago
Thanks for filing the ticket.
I have spent some time on this issue, and found that the issue should have something to do with backend swtpm configuration.
After the successfully test, re-run the test will fail with below error:
WARNING:esys:src/tss2-esys/api/Esys_CreatePrimary.c:400:Esys_CreatePrimary_Finish() Received TPM Error
ERROR:esys:src/tss2-esys/api/Esys_CreatePrimary.c:135:Esys_CreatePrimary() Esys Finish ErrorCode (0x000009a2)
Error: Generating key failed
Key could not be generated.
tpm2_rc_decode -V 0x000009a2¶
tpm:session(1):authorization failure without DA implications
It shows auth failure there.
I will try to ask for tool team's help to fix it.
Updated by rfan1 over 2 years ago
- Related to action #107044: [sle][security][sle15sp4][swtpm] test fails in tpm2_engine_rsa_operation added
Updated by rfan1 over 2 years ago
- Related to action #107155: [tools][tw][sle][QEMUTPM][tpm2.0] swtpm devices need to be clear once test done added
Updated by dimstar over 2 years ago
That test was added to Tumbleweed on around February 13 (first test run in group 1)
Since then, we had daily snapshots and 4 test runs passed - the rest all failed.
I suggest to move this test (back) to the devel group where it can be worked on without blocking product testing (test was never stable, should never have gone out of the devel group)
The issue was fixed now, I will update more information once getting feedback from poo#107155
Updated by rfan1 over 2 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 80
Updated by rfan1 over 2 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100