Project

General

Profile

Actions
Copy link

action #67105

closed

[sle][security][sle15sp2][FIPS] test fails in seahorse_sshkey: no 'seahorse-display-sshkey' needle matched

Added by llzhao almost 4 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
bchou
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-05-21
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP2-Online-x86_64-fips_ker_mode_tests_crypt_x11@64bit fails in
seahorse_sshkey

Test suite description

Maintainer: bchou@suse.com ISO_5=SLE-%VERSION%-WE-DVD-x86_64-Build%BUILD_WE%-Media1.iso

Reproducible

Fails since (at least) Build 97.1

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by bchou almost 4 years ago

  • Status changed from New to In Progress

It Looks like the race condition problem.

Actions
Copy link
 #2

Updated by bchou almost 4 years ago

[PASSED] 195.1 (Public RC2) : id_rsa was created
[FAILED] 197.1 : fail at permission denied
[FAILED] 202.6 (RC3) : id_rsa.1　was created

The problem could be the default name was changed. Doing some manual tests to confirm again.

Actions
Copy link
 #3

Updated by bchou almost 4 years ago

Do some investigate that it could be the default ssh key was created already in the system, that's why it creates a new key with new key name if we do not specify a ssh key name. It shows the sequence accordingly, such as id_rsa, id_rsa.1, id_rsa.2, id_rsa.3 ...etc. We could need to change the original needles since the match area are fixed for id_rsa, it could get the fail if the system with more than one ssh key in the begining. I just do some manual tests, and the ssh key is created without a problem.

Actions
Copy link
 #4

Updated by rfan1 almost 4 years ago

So, what is the solution?

removing the existing key files or reuse it/them if any?

Actions
Copy link
 #5

Updated by bchou almost 4 years ago

  • Status changed from In Progress to Resolved

We just discuss it via Rocket.Chat and I think we can reuse the original Needle and do the adjustments for the compare area. Because we used the image from create_hdd_gnome, the default ssh key could be added probably from the functional group for other testing purposes. For this case, we just need to check the ssh key can be added via seahorse under FIPS mode. Simply needles adjustment is acceptable.

Rerun from SLES15 SP2 202.6 build with new needles.
fips_env_mode_tests_crypt_x11 : https://openqa.suse.de/tests/4291027#step/seahorse_sshkey/16
fips_ker_mode_tests_crypt_x11 : https://openqa.suse.de/tests/4290993#step/seahorse_sshkey/16

Thanks a lot.

Actions
Copy link
 #6

Updated by bchou about 2 years ago

  • Description updated (diff)
Actions
Copy link

Also available in: Atom PDF