[autobackport: sssd-2-10] ci: add TMT plan for passkey testing in PRCI#8726
Conversation
|
Failed to load packit config file: For more info, please check out the documentation or contact the Packit team. You can also use our CLI command |
There was a problem hiding this comment.
Code Review
This pull request introduces a new TMT test plan for SSSD passkey functionality and updates the Packit configuration to include automated testing, downstream proposals, and Koji builds. However, the reviewer identified critical issues that must be addressed: the .packit.yaml file contains unresolved git conflict markers that render the configuration invalid, and the test plan's repository cloning logic incorrectly defaults to the master branch instead of the appropriate stable branch for this backport.
6aa7c75 to
ce7f546
Compare
|
/packit test |
|
CI failures are unrelated |
Add comprehensive TMT plan for testing SSSD passkey functionality across IPA, LDAP, and Samba identity providers using containerized environments. Signed-off-by: Iker Pedrosa <ipedrosa@redhat.com> Co-authored-by: Claude Sonnet 4 <noreply@anthropic.com> Reviewed-by: Jakub Vávra <jvavra@redhat.com> Reviewed-by: Justin Stephenson <jstephen@redhat.com> (cherry picked from commit d54cf52)
Enable automated passkey testing on pull requests after COPR builds complete. Tests run on centos-stream-10 target using the TMT plan. Signed-off-by: Iker Pedrosa <ipedrosa@redhat.com> Co-Authored-By: Claude Sonnet 4 <noreply@anthropic.com> Reviewed-by: Jakub Vávra <jvavra@redhat.com> Reviewed-by: Justin Stephenson <jstephen@redhat.com> (cherry picked from commit 210f50f)
If COPR_ENABLE_CMD fails, the script will now fail immediately instead of proceeding to dnf upgrade with packages from default repositories, ensuring tests run against the correct SSSD version. Signed-off-by: Iker Pedrosa <ipedrosa@redhat.com> Reviewed-by: Jakub Vávra <jvavra@redhat.com> Reviewed-by: Justin Stephenson <jstephen@redhat.com> (cherry picked from commit 334449b)
Update passkey.fmf to use the `hardware.memory` specification. Changed from fixed 16GB to ">= 16 GB" requirement as per Testing Farm documentation at https://docs.testing-farm.io/Testing%20Farm/0.1/test-request.html#ram Signed-off-by: Iker Pedrosa <ipedrosa@redhat.com> Reviewed-by: Jakub Vávra <jvavra@redhat.com> Reviewed-by: Justin Stephenson <jstephen@redhat.com> (cherry picked from commit 167b5a9)
With 16GB RAM allocation, CentOS Stream 10 tests can now run directly on matching VM and containers. Thus, update the plan to take this into account and detect the distribution accordingly. Signed-off-by: Iker Pedrosa <ipedrosa@redhat.com> Reviewed-by: Jakub Vávra <jvavra@redhat.com> Reviewed-by: Justin Stephenson <jstephen@redhat.com> (cherry picked from commit 943ecbb)
|
The pull request was accepted by @justin-stephenson with the following PR CI status: 🟢 CodeQL (success) There are unsuccessful or unfinished checks. Make sure that the failures are not related to this pull request before merging. |
29f337f to
df797a9
Compare
This is an automatic backport of PR#8672 ci: add TMT plan for passkey testing in PRCI to branch sssd-2-10, created by @ikerexxe.
Caution
@ikerexxe The patches did not apply cleanly. It is necessary to resolve conflicts before merging this pull request. Commits that introduced conflict are marked with
CONFLICT!.You can push changes to this pull request
Original commits
d54cf52 - tests: add TMT plan for passkey testing
210f50f - ci: add TMT passkey tests to packit workflow
Backported commits
Conflicting Files Information (check for deleted and re-added files)
Original Pull Request Body
Summary
This PR introduces testing infrastructure for SSSD passkey functionality using TMT and testing farm. It is designed to automate verification across diverse environments and integrate directly into the existing Packit CI workflow.
Changes Made
Test Plan
The TMT plan follows an automated lifecycle for each PR:
Constraints & known limitations
fedora-all, containers inherit the distribution of the host VM (e.g., F44 VM hosts F44 containers). This approach links test stability to the target distribution’s stability. Rawhide environments may occasionally experience failures due to upstream shifts unrelated to SSSD.Observability & debugging
If a test fails, kKey data can be found at:
tmt-logand test artifacts directory:plans/passkey/data/artifacts/tests/Final notes