QA (public) » openQA Project (public) » openQA Tests (public) » Containers and images

culprit found . Investigation together with developer https://suse.slack.com/archives/C02CLB8TZP1/p1730125329223979

17m
Marcus Meissner usually what happens is if you crearted the image with Legacy module enabled, but do not have Legacy testing enabled

[8:55 AM]
Marcus Meissner so and if you look at the zypper.log

[8:55 AM]
Marcus Meissner i see TEST_0 with BASESYSTEM from the incident

[8:55 AM]
Marcus Meissner but there is no TEST_1 with LEGACY from the incident

[8:56 AM]
Marcus Meissner so your test needs to somehow specifcy TEST_1 as Legacy from the SUSE Maintenance ijncident

[8:56 AM]
Marcus Meissner so testcase issue

There was a code change that registers legacy module

[2024-10-29T21:24:10.743606Z] [debug] [pid:125824] tests/fips/openssl/openssl_fips_alglist.pm:81 called security::openssl_misc_utils::install_openssl -> lib/security/openssl_misc_utils.pm:54 called registration::add_suseconnect_product -> lib/registration.pm:201 called testapi::record_info
[2024-10-29T21:24:10.743703Z] [debug] [pid:125824] <<< testapi::record_info(title="SCC product", output="Activating product sle-module-legacy", result="ok")
[2024-10-29T21:24:10.743921Z] [debug] [pid:125824] tests/fips/openssl/openssl_fips_alglist.pm:81 called security::openssl_misc_utils::install_openssl -> lib/security/openssl_misc_utils.pm:54 called registration::add_suseconnect_product -> lib/registration.pm:208 called (eval) -> lib/registration.pm:208 called testapi::assert_script_run
[2024-10-29T21:24:10.744034Z] [debug] [pid:125824] <<< testapi::assert_script_run(cmd="SUSEConnect  -p sle-module-legacy/\${VERSION_ID}/\${CPU} ", timeout=300, quiet=undef, fail_message="")
[2024-10-29T21:24:10.744144Z] [debug] [pid:125824] tests/fips/openssl/openssl_fips_alglist.pm:81 called security::openssl_misc_utils::install_openssl -> lib/security/openssl_misc_utils.pm:54 called registration::add_suseconnect_product -> lib/registration.pm:208 called (eval) -> lib/registration.pm:208 called testapi::assert_script_run

It seems this used to work at https://openqa.suse.de/tests/15759501 but started failing at https://openqa.suse.de/tests/15766952 without test code changes at this point (only last_good_build retry works).

This is probably related to the openssl-1_1 update https://smelt.suse.de/incident/36134/.

It is not failing for us at https://openqa.suse.de/tests/15806493, but this is the first time after the code changes for a combination of a) new openssl-1_1 update and b) a product without Legacy module.

I have filed ticket #169087 for investigating this from our side.

If legacy is required for openssl1_1 then it should be enabled, and we have simply avoided it before because there was no direct dependency nor need

Any updates on this ticket?

@asmorodskyi ping?