Add Rocky Linux 9 support

[lumarel]

What does this PR change?

This PR should make Rocky Linux 9 work completely.

I hope I didn't miss something took me a while to get through all parts of the application.

The only thing I didn't add are the parts in the 2 additional_products.json files and the referencing repo templates in mgr-bootstrap-data.py, as I didn't know which IDs I would have had to set. If you could tell me which I should set there I can of course also add this right away 🙂

It also adds the EPEL 9 key to the schema as this hasn't been done up to now, as far as I can see.

GUI diff

No difference.

Documentation

• Documentation issue was created: uyuni-docs#1661

• (OPTIONAL) Documentation PR

• [ ] DONE

Test coverage

• No tests: already covered

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

• [x] DONE

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

I don't really know which tests to run.

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"

[lumarel]

@juliogonzalez

Sorry I didn't have the time to test that yesterday then, was quite late, will change the few things this evening and run some tests, thank you for the guidance I wouldn't have known how to do them anyway 🙂

[juliogonzalez]

@juliogonzalez

Sorry I didn't have the time to test that yesterday then, was quite late, will change the few things this evening and run some tests, thank you for the guidance I wouldn't have known how to do them anyway slightly_smiling_face

One day I will write a quick dock about how to build the packages.

But for now it's easier if you find each of the file names at the server with find, and then replace (always remember to stop services first). That's what I do for quick testing.

[lumarel]

I already know where most of the files are, due to me reverse engineering here and there (as I didn't understand why something was not working), so I think I will find the files quite easily only the compiled java stuff is a bit of a hard part for me 🙂

I unfortunately don't have a running Uyuni DEV system right now, and also failed to set one up today (only have RL8 dev systems), so tomorrow I will give it another one... hopefully no more hostname failures 🙂

[lumarel]

@juliogonzalez I got a system running again! And tested the stuff, looks good, only was a bit finicky as the bootstrap and common-channels files look to have changed quite a bit during die month 🙂

(I couldn't test a client, as there is no venv package for el9 right now)

[lumarel]

Rebasing done 🙂

[lumarel]

Another rebase, is there something more to do?

[lumarel]

@juliogonzalez Thank you for the notification! I rebased onto master now and changed the *.changes files.

And as you asked in the beginning about the Raspberry Pi stuff, I also added the altarch repos now, so if someone wants to play around with raspbis now, that should be easier now 👀 (it's fully ready now)

[lumarel]

@juliogonzalez Fixed the conflicts again

[juliogonzalez]

@lumarel I approved, but just added mc as reviewer for the Java part, just in case.

Do not worry about the changelogs (unless mc requests more fixes), I will take care of fixing the conflicts for them.

[lumarel]

Thank you two! 🙂