Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-29003

Default Internal Registry cleans custom images stored on it from 4.13 to 4.14

XMLWordPrintable

    • +
    • Important
    • Yes
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      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.

              fmissi Flavian Missi
              rhn-support-hgomes Hevellyn Gomes
              Wen Wang Wen Wang
              Votes:
              0 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: