-
Feature Request
-
Resolution: Done
-
Major
-
None
-
4.17
-
None
-
None
-
Future Sustainability
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
-
None
-
None
-
None
Proposed title of this feature request: Cherry-pick an upstream podman patch to OpenShift 4.17
What is the nature and description of the request? Stability improvement to OpenShift 4.17
Why does the customer need this? Customer needs the improved `podman system check --quick` to do image repair at node startup.
List any affected packages or components: podman , cri-o
The feature is already in podman *main* branch, but not in 5.2.x yet. It will need to be cherry-picked to 5.2.* first before getting into OCP release. So, to clarify, here are the things that we need:
1. Cherry-pick https://github.com/containers/podman/pull/26272 to podman 5.2.x and release a new 5.2.x+1 version.
2. Update OCP to use this podman 5.2.x+1.
What is the business impact? Currently our business is suffering from instability of crio image corruption, and we need to mitigate this with a podman feature (podman system check) but this feature is too slow and to improve it we need to cherry-pick https://github.com/containers/podman/pull/26272
- is related to
-
OCPBUGS-57532 [podman-5.6] Customer needs the improved `podman system check --quick` to do image repair at node startup.
-
- Closed
-
- relates to
-
-
- Release Pending
-
-
-
- Closed
-
-
-
- Closed
-
