Actions
action #135461
closed[security] [15sp4] [15sp5] mutex wait timeout in krb5_crypt_prepare
Start date:
2023-09-11
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
Actions
Added by emiler over 1 year ago. Updated over 1 year ago.
0%
Description
We suspected it's related to https://progress.opensuse.org/issues/134282, but the new fixes do not affect this, despite using the right workers. It fails during mutex wait for other machines.
the other test suite is not scheduled: fips_tests_crypt_krb5_server, in dependencies tabs should be visible all connections.
Tried to run fips_tests_crypt_krb5_server parallel with fips_tests_crypt_krb5_kdc:
https://openqa.suse.de/tests/12200936
but ran into the same problem: test execution exceeded MAX_JOB_TIME
Note in QU it now failed at https://openqa.suse.de/tests/12302112# "krb5_crypt_nfs_server" - Antonios Pappas reported remaining NFS problems over at SAP/HA side, maybe it's related to that.
@tjyrinki_suse : Thanks for noticing, but I don't think the two cases are related.
In https://openqa.suse.de/tests/12302112 they had connectivity issues. zypper in failed due to this:
2023-09-26 01:48:28 <5> krb5server(4144) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):977 THROW: Download (curl) error for 'https://updates.suse.com/SUSE/Products/SLE-Module-Basesystem/15-SP5/x86_64/product/x86_64/nfs-kernel-server-2.1.1-150500.20.2.x86_64.rpm?grpTmBnWUP2VU9Cph5EsBkkYvf-oFOgQLxO28jd2O-P4O_Sfb_DQvr5v-UnAmf7J3jqHKqFqo6xoWMvouXUAYMzdI_sIpLoRuOPauRvIiOGcCEQsNu-g6BuLC_WjknKIZVFh3Xeqq2VdOIlagxJcnJAW815FG4sB':
2023-09-26 01:48:28 <5> krb5server(4144) [zypp-core] Exception.cc(log):186 Error code: Connection failed
2023-09-26 01:48:28 <5> krb5server(4144) [zypp-core] Exception.cc(log):186 Error message: Failed to connect to updates.suse.com port 443 after 18463 ms: Couldn't connect to server
Looks like the tests are passing now:
kdc: https://openqa.suse.de/tests/12313048
server: https://openqa.suse.de/tests/12313126
client: https://openqa.suse.de/tests/12313137
The tests are running normally. It is unknown what the "fix" was, but I personally think that it was infra related.