Refactor: Eliminate minima Binary and Sync Execution from Inside Server Container

[srbarrios]

Description

The current Salt states for test packages setup in server_containerized includes hardcoded downloading, unpacking, config templating, and execution of minima inside the container, via mgrctl.

We should not alter the container images, and we should not run additional processes inside it.

{% if grains.get('testsuite') | default(false, true) %}
mgrctl exec 'curl ...'
mgrctl exec 'tar ...'
mgrctl exec 'minima sync ...'
mgrctl cp ...

🎯 Goal

• Completely remove minima binary usage from inside the container.
• Instead:
  • Run minima sync outside the container (host or init container).
  • Mount the synced test repositories into the server container via a volume.

✅ Acceptance Criteria

• minima binary and sync logic is moved outside the podman container.
• Documented clear separation between test data provisioning and container deployment.

---

Originally posted by @srbarrios in #1832 (review)

[NamelessOne91]

Just to give some context:

The PR itself was mainly needed to unblock devs on some work at the time. We were running BVs in that period, so it ended up staying on the sidelines to avoid introducing breaking changes.
While at it, I noticed we still were relying on old minima versions (plural: we had 2 different ones) binaries being installed and decided to have at least everything running on the latest.

That said, I do agree with your comment as I find the current setup to be def. not ideal.

[maximenoel8]

Seeing this minima calls for testsuite I wonder why we are doing it that way.
Could it be possible to completely remove minima dependency for the server ?
Would it be better to have custom repository in testsuite/core + use of mirror urls ?

[maximenoel8]

List test packages in minima repo ( http://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Test-Packages:/Updates/rpm/x86_64/ )

• blackhole-dummy-1.0-1.1.x86_64.rpm
• hoag-dummy-1.1-1.1.x86_64.rpm
• milkyway-dummy-2.0-1.1.x86_64.rpm
• orion-dummy-1.1-1.1.x86_64.rpm
• perseus-dummy-1.1-1.1.x86_64.rpm
• rute-dummy-2.0-1.1.x86_64.rpm
• rute-dummy-2.0-1.2.x86_64.rpm
• rute-dummy-2.1-1.1.x86_64.rpm

List package in repo testsuite (http://minima-mirror-ci-bv.mgr.suse.de/repositories/systemsmanagement:/Uyuni:/Test-Packages:/Pool/rpm/x86_64/) (this url is KO from code )

• milkyway-dummy-1.0-1.1.x86_64.rpm
• rute-dummy-1.0-2.2.x86_64.rpm
• andromeda-dummy-1.0-1.2.noarch.rpm
• publishkey-helper-1.0-1.1.noarch.rpm
• virgo-dummy-1.0-1.2.noarch.rpm

We installed in default/testsuite.sls those packages:
- andromeda-dummy
- milkyway-dummy
- virgo-dummy

For me if we change: https://github.com/uyuni-project/uyuni/blob/b32d5ba7aaa2ffa2abd1506b27f1006f1f78606f/testsuite/features/reposync/srv_create_repository.feature and instead of localhost here we use the mirror repo, we can get ride of this minima setup. Or we copy the files from mounted mirror to the correct place if we want to keep localhost.

I'm pretty sure we can do it without minima.

[srbarrios]

For me if we change: https://github.com/uyuni-project/uyuni/blob/b32d5ba7aaa2ffa2abd1506b27f1006f1f78606f/testsuite/features/reposync/srv_create_repository.feature and instead of localhost here we use the mirror repo, we can get ride of this minima setup. Or we copy the files from mounted mirror to the correct place if we want to keep localhost.

I'm pretty sure we can do it without minima.

Brilliant, yes, I would follow that path.
I took the issue from a wrong angle.

Feel free to edit the card if you like.