Open
Labels
topic:testingUnit, integration, regression, conformance, E2E tests, coverage, flakes, and test infrastructure.Unit, integration, regression, conformance, E2E tests, coverage, flakes, and test infrastructure.
Description
User Story
As a maintainer retiring e2e/rust, I want the provider refresh handle test to run on rootless Podman, so the rotation and revocation path is covered on every local driver configuration we support.
Description
#5729 ports provider_refresh_handles::long_running_process_survives_rotations_and_reconfigure_revokes to tests/suites/features/provider-refresh. It adds CI rows only for Podman rootful and Docker rootful, after repeated local passes on each. The legacy test never ran in CI: it was left out of PODMAN_CI_TESTS while it was being stabilized.
Run the ported test on fedora-podman-rootless repeatedly. Fix any failure, or file it as a bug. Then add the row to .github/workflows/e2e-suites.yml.
Context
- Part of test: retire the old e2e test system onto testkit #5281. Follows test(e2e): port gateway-configuration tests that need no restart from e2e/rust to feature suites #5729.
- The test serves an OAuth token endpoint on
127.0.0.1in the test VM, which the gateway calls, and a resource onhost.openshell.internal, which the sandbox calls.
Definition of Done
- The test passes repeatedly on
fedora-podman-rootless, or each failure has its own issue. -
e2e-suites.ymlhas afeatures/provider-refreshrow onfedora-podman-rootless.
Metadata
Metadata
Assignees
Labels
topic:testingUnit, integration, regression, conformance, E2E tests, coverage, flakes, and test infrastructure.Unit, integration, regression, conformance, E2E tests, coverage, flakes, and test infrastructure.
Activity