Created attachment 1984327 [details] backup stage issue Description of problem: Indirect migration stuck on backup stage, due to invalid image name error Version-Release number of selected component (if applicable): MTC 1.8.0 How reproducible: Always Steps to Reproduce: 1. Create an indirect migration 2. Execute the migration Actual results: The migration is stuck on the backup stage. Expected results: The migration should be completed successfully. Additional info: describe pod logs: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 5m36s default-scheduler Successfully assigned test-django/stage-postgresql-2p8cv to ip-10-0-67-177.us-east-2.compute.internal Normal SuccessfulAttachVolume 5m33s attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-4663bbe1-b0d3-455d-87b5-9f8d5520599c" Normal AddedInterface 5m29s multus Add eth0 [10.129.2.119/23] from openshift-sdn Warning Failed 3m31s (x12 over 5m29s) kubelet Error: InvalidImageName Warning InspectFailed 24s (x27 over 5m29s) kubelet Failed to apply default image tag "registry.redhat.io/rhmtc/:": couldn't parse image reference "registry.redhat.io/rhmtc/:": invalid reference format
Going to update this to use rsync-transfer image rather than velero restic helper image
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