Ci add scc mirror

[jordimassaguerpla]

What does this PR change?

add description

GUI diff

No difference.

Before:

After:

• DONE

Documentation

• No documentation needed: add explanation. This can't be used if there is a GUI diff

• No documentation needed: only internal and user invisible changes

• Documentation issue was created: Link for SUSE Manager contributors, Link for community contributors.

• API documentation added: please review the Wiki page Writing Documentation for the API if you have any changes to API documentation.

• (OPTIONAL) Documentation PR

• DONE

Test coverage

ℹ️ If a major new functionality is added, it is strongly recommended that tests for the new functionality are added to the Cucumber test suite

• No tests: add explanation

• No tests: already covered

• Unit tests were added

• Cucumber tests were added

• DONE

Links

Issue(s): #
Port(s): # add downstream PR(s), if any

• DONE

Changelogs

Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository

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"

Before you merge

Check How to branch and merge properly!

[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/9490/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/9490/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. ⚠️

[github-actions]

Suggested tests to cover this Pull Request

• srv_sync_channels
• min_check_patches_install
• srv_advanced_search
• srv_cobbler_distro
• srv_reportdb
• srv_cobbler_profile
• allcli_update_activationkeys
• srv_maintenance_windows
• srv_manage_channels_page
• min_bootstrap_api
• srv_power_management_api
• srv_wait_for_reposync
• srv_user_configuration_salt_states

[jordimassaguerpla]

This adds 14% more tests, compared to the ones that run on master with gh actions vs master with jenkins. We will be at 56% , aprox.

[jordimassaguerpla]

Scenario: Add openSUSE Leap 15.5 product, including Uyuni Client Tools fails from time to time. Mirroring the uyuni client tools repos will add stability. I have added this in https://github.com/SUSE/spacewalk/issues/25950

[jordimassaguerpla]

Tests passed once. Triggering a second run to test stability.

[jordimassaguerpla]

tests passed. Triggering again...

[jordimassaguerpla]

one failure:

Scenario:Add new sources and promote again

This scenario ran at: 2024-12-12 21:04:02 +0000

WhenI follow the left menu "Content Lifecycle > Projects"
AndI follow "clp_name"
ThenI should see a "Build (0)" text
WhenI click on "Attach/Detach Sources"
AndI uncheck "Vendors"
AndI enter "Fake-Base-Channel-SUSE-like" in the placeholder "Search a channel"
AndI add the "Fake-Base-Channel-SUSE-like" channel to sources
AndI click on "Save"
ThenI wait until I see "Fake-Base-Channel-SUSE-like" text

Text 'Fake-Base-Channel-SUSE-like' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:40:in `/^I wait until I see "([^"]*)" text$/'
features/secondary/srv_content_lifecycle.feature:183:in `I wait until I see "Fake-Base-Channel-SUSE-like" text'

[jordimassaguerpla]

triggering again....

[jordimassaguerpla]

Now it passed...

[jordimassaguerpla]

Now it passed

[jordimassaguerpla]

it passed again