Actions
action #47024
closed[sle][security][sle15sp1] test fails in gpg - no candidate needle with tag(s) 'key-generation-failed' matched
Start date:
2019-02-02
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
It is expected to be failed in the case key_size==1024, but it is not.
Observation¶
openQA test in scenario OpenQA::Schema::Result::TestSuites=HASH(0xb2941a0) fails in
gpg
Reproducible¶
Fails since (at least) Build 141.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by whdu about 5 years ago
- Subject changed from test fails in gpg - no candidate needle with tag(s) 'key-generation-failed' matched to [sle][security][sle15sp1] test fails in gpg - no candidate needle with tag(s) 'key-generation-failed' matched
Updated by bchou about 5 years ago
- Status changed from New to Workable
gpg output fail due to RSA key fail in the previous build. It looks the issue was fixed in Beta3, so the gpg need to be tested in openQA currently.
Updated by bchou about 5 years ago
This should also related a bug
https://bugzilla.suse.com/show_bug.cgi?id=1125740
1125740 - [FIPS][Build 158.4] 1024 bit RSA keysize is still generated via gpg2 in fips mode
Updated by bchou about 5 years ago
- Status changed from Workable to In Progress
Developer confirmed the test are correct.
This needs to be fixed on the libgcrypt side.
Updated by bchou about 5 years ago
- Status changed from In Progress to Resolved
Let's wait for the bug fixing. Thanks.
Actions