Add tmt integration plan

[LecrisUT]

See:

• Propose podman friends integration plan in relevant repos teemtee/tmt#4047
• Add plan and test for container tools integration testing teemtee/tmt#4026
• Add tmt integration plan crun#1881
• Add tmt integration plan container-selinux#410

An alternative design is to add the tests in .packit.yaml. Let me know which approach would be preferred. I don't quite follow the steps you do with podman-next*.repo, maybe we could look into that as well?

(should use only one PR where we discuss and test these)

[openshift-ci]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: LecrisUT
Once this PR has been reviewed and has the lgtm label, please assign luap99 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[packit-as-a-service]

[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore.

[packit-as-a-service]

[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore.

[packit-as-a-service]

[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore.

[packit-as-a-service]

[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore.

[lsm5]

@LecrisUT change itself looks good, but over here it would be preferable to add a separate set of jobs in .packit.yaml and have some github IDs included in failure notifications, like what's done for cockpit revdep tests.

@containers/podman-maintainers PTAL, wdyt? This is another set of revdep tests, this time for TMT project itself.

[lsm5]

@LecrisUT change itself looks good, but over here it would be preferable to add a separate set of jobs in .packit.yaml and have some github IDs included in failure notifications, like what's done for cockpit revdep tests.

I'd say no need to include podman-next repo in the additional job if it keeps things simpler for now. We're already catching crun and container-selinux issues in those projects.

[LecrisUT]

@lsm5 someone better to ping for these. avc stuff would be hard for us to decipher, but not sure if those are the time of failures expected there.

[lsm5]

This works for me if it works for @psss . Does @thrix wanna be included here?

[Luap99]

This would fall under the same rules as the cockpit tests, packit is non blocking for us so we won't gate merges on this and most maintainers will not lock at these failures as they fail to often for unrelated reasons.
As such it is up to you (or @psss I guess as you added his ping to the failure message) to react on the ping and tell the author/maintainers that this PR is actually breaking something for tmt usage.