QE: Adapt BV test suite code for Uyuni BV

[nodeg]

What does this PR change?

This will

• adapt our BV test suite code for the Uyuni BV
• add verbosity to service restart commands
• add systemctl reload step

GUI diff

No difference.

• DONE

Documentation

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

Test coverage

• Cucumber tests were edited
• DONE

Links

• https://github.com/SUSE/spacewalk/issues/16082
• Manager 4.3: https://github.com/SUSE/spacewalk/pull/22408
• 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"

[Bischoff]

see comments

[srbarrios]

Please remove the commit to remove Ubuntu 18.04 from this PR.
This is out of scope, and already covered by #7398

[nodeg]

Rebase done.

[nodeg]

The failed test is a flaky one.

[Bischoff]

one more nitpick and we're good

[nodeg]

The old array syntax work as expected:

When(/^I execute doms test for "([^"]*)"$/) do |client|
 base_channel = BASE_CHANNEL_BY_CLIENT[product][client]
 channel = CHANNEL_TO_SYNC_BY_BASE_CHANNEL[product][base_channel]
 parent_channel = PARENT_CHANNEL_TO_SYNC_BY_BASE_CHANNEL[product][base_channel]
 puts base_channel
 puts channel
 puts parent_channel # <--- nil in our case
end

Feature: doms test

  Scenario: Test new constant            # features/dom.feature:6
      This scenario ran at: 2023-08-29 09:24:56 +0200
openSUSE Leap 15.4 (x86_64)
openSUSE-Leap-15.4-x86_64-uyuni

    When I execute doms test for "proxy" # features/step_definitions/common_steps.rb:536
      This scenario took: 1 seconds

1 scenario (1 passed)
1 step (1 passed)
0m0.849s

[nodeg]

Yes, what I mean is that if there is only one entry "Uyuni Client Tools for AlmaLinux 9 (x86_64) (Development)" and there is no entry "Uyuni Client Tools for AlmaLinux 9 (x86_64)" for now. I think we better use "Uyuni Client Tools for AlmaLinux 9 (x86_64)" on this step, as this will select the same entry with or without this word appended, and once SCC change the sub-product name to "Uyuni Client Tools for AlmaLinux 9 (x86_64)" we will not need to update our code to adapt to it.

Now I got it. Makes sense, I will adjust the code.

[nodeg]

Waiting for the GitHub Actions before merging.

[nodeg]

Test are all good. I will squash some of the temporary commits and will directly merge after this.