QE: Multiple test framework refactors

[nodeg]

⚠️ ⚠️ ⚠️
Please don't squash commits. This is a special branch that combine multiple refactors, so we prefer to keep a commit per PR merged into this branch, to facilitate navigating over the reasons for each change.
⚠️ ⚠️ ⚠️

Prerequisites before merging this

• Use Ruby 3.3 for non Ubuntu/macOS openSUSE/twopence#81
• Controller: update Ruby to 3.3 for HEAD/Uyuni/Uyuni Podman/5.x sumaform#1248

What does this PR change?

• QE: Update Ruby version #6559
• Using a new user per feature, to facilitate parallelization of secondary_parallelizable.yml in CI #5743
• Refactor the communication with external machines using Ruby built-in libraries #9160
• Add timeout after step #9198
• QE: Fix wrong return value in scp method #9205
• Refactor Remote Node #9214
• Handling a reboot of a remote node through net-ssh, plus fixing scp command #9224
• Fixes related to RemoteNode implementation #9229
• Fix user in srv_mainpage #9231
• Filter by channel in CLM sources, before selecting it #9240
• Find the text of the event, instead of an event completed during last minute #9241
• Fix selection of channel in the sources of a CLM #9243

TODOs

• include fixes for the GitHub Actions PR tests for using Ruby 3
• ...

GUI diff

No difference.

• DONE

Documentation

• No documentation needed: only internal and user invisible changes
• DONE

Test coverage

• Cucumber tests were edited
• DONE

Links

Issue(s): #
Ports(s): #

• 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 "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/9181/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/9181/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. ⚠️

[vandabarata]

Thank you so much for all this work

[srbarrios]

⚠️
Please let's keep it as draft, until master is unlock.
As this PR will contain the combination of multiple PRs merged into qe-develop branch.

[nodeg]

GitHub PR acceptance tests:

Run ./testsuite/podman_runner/05_install_gems_in_controller.sh
+ sudo -i podman exec controller bash -c 'export GEM_PATH="/usr/lib64/ruby/gems/3.3.0"'
+ sudo -i podman exec controller bash -c 'cd /testsuite && bundle.ruby3.3 install --gemfile Gemfile --verbose'
bash: bundle.ruby3.3: command not found

For this to work, we need to update the controller container. However, this is not possible in this PR and would also affect the all other PRs. So for now, we cannot rely on the PR tests here.
I did run them in my fork, where

• all changes (Ruby 3, Gems, containers) are made in the master branch. See last commit there
• then I built all containers (https://github.com/nodeg/uyuni/actions/workflows/build_containers.yml)
• triggered a PR with minor changes to see if the tests work with the new code: Test Ruby 3 changes nodeg/uyuni#36

[nodeg]

Ok, so with the changes as of now, we have one error:

I will force push again so that the controller container will get updated only under certain conditions and not for every push to this PR like it is now.

[nodeg]

Rebase done.

[nodeg]

Another rebase to include mcs test suite fixes.