Add tmt tests

[ekohl]

Why are you introducing these changes? (Problem description, related links)

This is an experiment to see if tmt could be used to run tests. Under the hood Packit uses Testing Farm to run the built RPMs on VMs.

Last time I tried there were some limitations. Before I look at really make it run any tests, this is just a trivial setup.

What are the changes introduced in this pull request?

• Add a trivial tmt setup

How to test this pull request

Steps to reproduce:

• Let it run
• See if the output is useful

Checklist

• Tests added/updated (if applicable)
• Documentation updated (if applicable)

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ekohl]

Ok, this is now mostly working. The failure on the host is that it can't resolve its own hostname:

TASK [pulp : Configure Foreman Proxy] ******************************************
fatal: [localhost]: FAILED! => 
    changed: false
    msg: 'Failed to ensure entity state: ForemanApiException: Error while performing create
        on smart_proxies: 422 Client Error: Unprocessable Content for url: https://ip-172-31-23-45.us-east-2.compute.internal/api/smart_proxies
        - {''id'': None, ''errors'': {''base'': [''Unable to communicate with the proxy:
        ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([Socket::ResolutionError]:
        Failed to open TCP connection to ip-172-31-23-45.us-east-2.compute.internal:443
        (getaddrinfo: Name or service not known)) for proxy https://ip-172-31-23-45.us-east-2.compute.internal/pulp/api/v3/smart_proxy/v2/features'',
        ''Please check the proxy is configured and running on the host.'']}, ''full_messages'':
        [''Unable to communicate with the proxy: ERF12-2530 [ProxyAPI::ProxyException]:
        Unable to detect features ([Socket::ResolutionError]: Failed to open TCP connection
        to ip-172-31-23-45.us-east-2.compute.internal:443 (getaddrinfo: Name or service
        not known)) for proxy https://ip-172-31-23-45.us-east-2.compute.internal/pulp/api/v3/smart_proxy/v2/features'',
        ''Please check the proxy is configured and running on the host.'']}'

It does have some quirks. Biggest is that you can't run RHEL on the public ranch. Then the test appears to be match to the copr chroot so you need to build for CentOS Stream too.

It also needs some hacks to enable the right chroots. That triggered me to write rpm-software-management/dnf-plugins-core#627. It'll likely be a while before that is available, if ever.