Description of problem: On migrating an application to the target cluster, the migrated app fails to pull image from the internal image registry resulting in application failure. Version-Release number of selected component (if applicable): 4.11 -> 4.13 AWS How reproducible: Always Steps to Reproduce: 1. Deploy django application in source cluster 2. Trigger a migration through a migplan from UI/Backend. 3. Validate the app in target cluster Actual results: App pods showing imagepullbackoff not being able to pull image from internal image registry. Expected results: App to work fine. Additional info: Normal Pulling 2m42s (x2 over 2m55s) kubelet Pulling image "image-registry.openshift-image-registry.svc:5000/django/django-psql-persistent@sha256:9a94a8c27e000ec351bcc73333cebcacfb1cf15ced36b83a06a827e50804b7de" Warning Failed 2m42s (x2 over 2m55s) kubelet Failed to pull image "image-registry.openshift-image-registry.svc:5000/django/django-psql-persistent@sha256:9a94a8c27e000ec351bcc73333cebcacfb1cf15ced36b83a06a827e50804b7de": rpc error: code = Unknown desc = unable to retrieve auth token: invalid username/password: authentication required Warning Failed 2m42s (x2 over 2m55s) kubelet Error: ErrImagePull
Can you please tell us if this application was migrated with direct image migration or indirect image migration?
@
Observed this behaviour with both Direct Image and Indirect Image migration.
https://github.com/migtools/velero-plugin-for-mtc/commit/db70a40735eafe5f49d632d16bbd317579059689
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Migration Toolkit for Containers (MTC) 1.8.0 security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:5447