action #135401
closed
[security] fips pattern missing because basesystem repository not available
Added by tjyrinki_suse 8 months ago.
Updated 6 months ago.
Category:
Bugs in existing tests
Description
openQA test in scenario sle-15-SP6-Online-x86_64-fips_env_stunnel_server@64bit fails in
fips_setup
Fails since (at least) Build 19.1 (current job)
Last good: 16.1 (or more recent)
First thought to be a product problem, developer explained that
as this you install with the Online medium, you need to enable the Basesystem Pool repository.
Comparing a passing run at https://openqa.suse.de/tests/11979771#settings to now failing run at https://openqa.suse.de/tests/12036081#settings , it seems the failing run is here where there are 50+ repository related settings that did not exist for the passing one.
Looking further back to 15-SP5 - https://openqa.suse.de/tests/11175701#settings - it seems the new case of having all of those settings would be the right way, but the question for this ticket is why it does not work?
according to logs:
[2023-09-07T12:25:11.461464+02:00] [debug] [pid:87738] <<< distribution::script_output("script failed with : \nL_NVX\nSUSEConnect error: Get \"http://all-19.1.proxy.scc.suse.de/connect/systems/activations\": dial tcp: lookup all-19.1.proxy.scc.suse.de: i/o timeout\nSCRIPT_FINISHEDL_NVX-1-")
so we cannot connect the reg server and we don't match any of the code paths (see variable matching $sc_out in test_repo_setup.pm) so to remediate it throw us to the path of adding the dvd repo,
so we never reach the normal path of registration, https://openqa.suse.de/tests/11979771#step/test_repo_setup/20
seems unrelated with settings, now we have correct settings like in previous GMC.
the path of adding the dvd doesn't work of course, because we use iso for the Online medium which doesn't have the base repo, we would need to schedule this in Full while MM is fixed, which probably doesn't worth it.
There are issues with MM not being able to reach outside, perhaps better work on this ticket when things are more clear.
- Status changed from Workable to Blocked
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: fips_ker_mode_Firefox
https://openqa.suse.de/tests/12305300#step/fips_setup/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: fips_ker_mariadb_ssl_client
https://openqa.suse.de/tests/12506113#step/fips_setup/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.
- Status changed from Blocked to Workable
The related p.o.o is now resolved.
The topic itself - FIPS repo seems available now, so this ticket is maybe no longer valid? It's "just" that everything FIPS fails as documented at bsc#1216059.
tjyrinki_suse wrote in #note-5:
The related p.o.o is now resolved.
The topic itself - FIPS repo seems available now, so this ticket is maybe no longer valid? It's "just" that everything FIPS fails as documented at bsc#1216059.
I agree, feel free to resolve it without assignee or reject it, how you would normally do.
- Status changed from Workable to Closed
Also available in: Atom
PDF