-
Bug
-
Resolution: Done
-
Major
-
4.14.0
-
None
-
No
-
CLOUD Sprint 241
-
1
-
Proposed
-
False
-
Description of problem:
Tests like lint and vet used to be ran within a container engine by default if an engine was detected, both locally and in CI.Up until now no container engine was detected in CI, so tests would run natively there.Now that the base image we use in CI has now started shipping `podman`, a container engine is detected by default and tests are run within podman by default. But creating nested containers doesn't work in CI at the moment and thus results in a test failure.As such we are switching the default behaviour for tests (both locally and in CI), where now by default no container engine is used to run tests, even if one is detected, but instead tests are run natively unless otherwise specifi
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- blocks
-
OCPBUGS-25458 Tests failing in CI since base image changes
- Closed
- is cloned by
-
OCPBUGS-25458 Tests failing in CI since base image changes
- Closed
- links to
(7 links to)