Fix uyuni proxy sync

[maximenoel8]

What does this PR change?

Uyuni product synchronized for proxy is not correct.

GUI diff

No difference.

• DONE

Documentation

• No documentation needed: only internal and user invisible changes

• 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: already covered

• DONE

Links

Port:
Issue:

• 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_lint_checkstyle"
• Re-run test "java_pgsql_tests"
• Re-run test "ruby_rubocop"
• 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/9439/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/9439/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. ⚠️

[srbarrios]

The channels synchronized seems correct, but.. I wonder at which point we include the correct repository for the mgr-tools (in particular mgrpxy) during the CI.
I guess... we only do it on sumaform, and we rely on it, right? If that's the case, maybe it gonna be good a comment somewhere in this feature to explain that we skip that step because we do directly on deployment.

zypper ar https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/images/repo/Uyuni-Proxy-POOL-x86_64-Media1/

[maximenoel8]

This is done during combustion.

[srbarrios]

But in combustion we might be passing Stable or Master as repos, but... not the one coming from the MIs, as far as I know we don't handle MI injections in combustion.

[maximenoel8]

Do you mean the repositories from additional_repository variable ?
We do now add those repositories into combustion: https://github.com/uyuni-project/sumaform/blob/addeb4382c1c77c2e84f8e7644d66319fa28361e/backend_modules/libvirt/host/combustion#L97C1-L105C5

That what trigger me to open this issue: https://github.com/SUSE/spacewalk/issues/25609