-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.14.0
This is a clone of issue OCPBUGS-29525. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-29003. The following is the description of the original issue:
—
Description of problem:
After upgrade from 4.13.x to 4.14.10, the workload images that the customer stored inside the internal registry are lost, resulting the applications pods into error "Back-off pulling image". Even when manually pulling with podman, it fails then with "manifest unknown" because the image cannot be found in the registry anymore. - This behavior was found and reproduced 100% on ARO clusters, where the internal registry is by default backed up by the Storage Account created by the ARO RP service principal, which is the Containers blob service. - I do not know if in non-managed Azure clusters or any other architecture the same behavior is found.
Version-Release number of selected component (if applicable):
4.14.10
How reproducible:
100% with an ARO cluster (Managed cluster)
Steps to Reproduce: Attached.
The workaround found so far is to rebuild the apps or re-import the images. But those tasks are lengthy and costly specially if it is a production cluster.
- clones
-
OCPBUGS-29525 Default Internal Registry cleans custom images stored on it from 4.13 to 4.14
- Closed
- is blocked by
-
OCPBUGS-29525 Default Internal Registry cleans custom images stored on it from 4.13 to 4.14
- Closed
- links to
-
RHBA-2024:1046 OpenShift Container Platform 4.14.z bug fix update