Description of problem: after editing the repolication reprepository, and adding a custom CA, and the repo is successfully connected, when triggerring a migration it fails on the backup phase Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Edit the replication repository and provide a custom CA 2. Wait for the connection to be successfull then close the edit panel 3. Create a new migration plan and trigger cutover Actual results: The migration fails on the backup phase Expected results: The migration should complete successfully Additional info: $ velero backup logs migration-4423c-initial-b248q --namespace openshift-migration An error occurred: Get "https://s3-ocs-storage.apps.cam-tgt-58680.qe.devcluster.openshift.com/migstorage/velero/backups/migration-4423c-initial-b248q/migration-4423c-initial-b248q-logs.gz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=dwR2E11Z0Avvz4bCm6xk%2F20231025%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20231025T135032Z&X-Amz-Expires=600&X-Amz-SignedHeaders=host&X-Amz-Signature=90da18440d92a19eb920027573bd09cd2f4e544b02af92f2b28e3554d91cca70": tls: failed to verify certificate: x509: certificate signed by unknown authority
https://github.com/migtools/mig-controller/pull/1359
Verified, The migraion with custom CA set to the mig storage is working as expected
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 (Moderate: Migration Toolkit for Containers (MTC) 1.8.2 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:7222