QE: Leap 15.5 is no longer supported. Switch to 15.6

[NamelessOne91]

What does this PR change?

The following products are now unsupported:

• Debian < 12
• Ubuntu < 20.04
• openSUSE Leap < 15.6
• SUMA < 4.2

Some CI tests are failing because they still check for Leap 15.5 channels. Let's switch to 15.6

GUI diff

No difference.

• DONE

Documentation

• No documentation needed: only internal and user invisible changes

• DONE

Test Coverage

• Cucumber tests were modified

• DONE

Links

Issue(s): //
Port(s): No port needed - change needed only for Uyuni/Head

• DONE

Changelogs

If you don't need a changelog check, please mark this checkbox:

• No changelog needed

If you uncheck the checkbox after the PR is created, you will need to re-run changelog_test (see below)

Re-run a test

If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run:

• Re-run test "changelog_test"
• Re-run test "backend_unittests_pgsql"
• Re-run test "java_pgsql_tests"
• Re-run test "schema_migration_test_pgsql"
• Re-run test "susemanager_unittests"
• Re-run test "javascript_lint"
• Re-run test "spacecmd_unittests"

[github-actions]

👋 Hello! Thanks for contributing to our project.
Acceptance tests will take some time (aprox. 1h), please be patient ☕

You can see the progress at the end of this page and at https://github.com/uyuni-project/uyuni/pull/9828/checks
Once tests finish, if they fail, you can check 👀 the cucumber report. See the link at the output of the action.
You can also check the artifacts section, which contains the logs at https://github.com/uyuni-project/uyuni/pull/9828/checks.

If you are unsure the failing tests are related to your code, you can check the "reference jobs". These are jobs that run on a scheduled time with code from master. If they fail for the same reason as your build, it means the tests or the infrastructure are broken. If they do not fail, but yours do, it means it is related to your code.

Reference tests:

• https://github.com/uyuni-project/uyuni/actions/workflows/acceptance_tests_secondary_parallel.yml?query=event%3Aschedule

• https://github.com/uyuni-project/uyuni/actions/workflows/acceptance_tests_secondary.yml?query=event%3Aschedule

KNOWN ISSUES

Sometimes the build can fail when pulling new jar files from download.opensuse.org . This is a known limitation. Given this happens rarely, when it does, all you need to do is rerun the test. Sorry for the inconvenience.

For more tips on troubleshooting, see the troubleshooting guide.

Happy hacking!
⚠️ You should not merge if acceptance tests fail to pass. ⚠️

[ktsamis]

No problem but check if there's any other place?

[NamelessOne91]

No problem but check if there's any other place?

Looking at CI's results and with a quick shift through the testsuite those seem to be the only places were things can break because we depend on a specific Leap version to be in the product list.
We do still use Leap 15.5 in a lot of places, but self-manage the channels.

[nodeg]

Is this really necessary right now? I am still able to see Leap 15.5 in the product wizard for 5.0.3. However, on HEAD they are missing. Is this only valid for Uyuni/HEAD?

5.0.3

HEAD

[mcalmer]

Is this only valid for Uyuni/HEAD?

Yes. Leap 15.5 and lower was disabled on 5.1 and later. 5.0 and earlier still have it

[nodeg]

Thank you, mc.