[Ansible] Ansible Managed entitlement and default playbook/inventory paths

[parlt91]

What does this PR change?

Enhancements to the existing Ansible integration

This PR implements the following points of https://github.com/SUSE/spacewalk/issues/25367

1. Set default paths for the playbook location (/etc/ansible/playbooks) and inventory file (/etc/ansible/hosts), so users don’t need to manually add them for every control node
2. Add filtering options on the system list page for Ansible-managed systems that are already onboarded in SUSE Manager.

I also decided to remove all existing Ansible paths for a control node when the Ansible Control Node entitlements is removed, to make the data we store in the db consistent and make managing Ansible Managed systems easier.

GUI diff

After:

Filter by System Type: Ansible Managed in the system list

Add Ansible Managed entitlement

Add new Inventory Refresh action

Add default playbook and inventory paths on adding a control node

• DONE

Documentation

• Documentation issue was created: [TODO]

• (OPTIONAL) Documentation PR

• DONE

Test coverage

• Unit tests were added

• Cucumber tests were added

• DONE

Links

Issue(s): https://github.com/SUSE/spacewalk/issues/25367

• 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"

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/9812/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/9812/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. ⚠️

[Etheryte]

Nothing to review on the frontend. It looks like there's a layout bug in the playbook directories input and related areas, do we have a ticket for that?

[parlt91]

Nothing to review on the frontend. It looks like there's a layout bug in the playbook directories input and related areas, do we have a ticket for that?

Card created https://github.com/SUSE/spacewalk/issues/26555

[cbbayburt]

I just tested the new code on my local env and everything works as they should 👍

Also, thanks for the nicely organized code and the commits. It makes the review much easier.

One thing I couldn't figure out is after I'm done testing the whole feature, somehow my clients could no longer access any channels anymore. I tried recreating the channels, re-registering clients with no success. I have absolutely no idea if it's caused by this patch at all, but I think it's something to be aware of. I'll try it once again with a fresh setup next week, and until I figure it out, I'll assume it's just a quirk in my setup.

@Etheryte, if you have the time to take care of the CSS issues mentioned above before the master is unlocked for the next release, feel free to just add a commit for the fix on top of this PR.