Bug 2246122

Summary:	Backup phase fails after setting custom CA replication repository
Product:	Migration Toolkit for Containers	Reporter:	mohamed <midays>
Component:	Controller	Assignee:	Dylan Murray <dymurray>
Status:	CLOSED ERRATA	QA Contact:	mohamed <midays>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	1.8.0	CC:	dymurray, rjohnson
Target Milestone:	---
Target Release:	1.8.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2342585 (view as bug list)		Environment:
Last Closed:	2023-11-15 01:25:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2342585

Description mohamed 2023-10-25 13:51:39 UTC

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

Comment 1 Dylan Murray 2023-10-25 18:57:50 UTC

https://github.com/migtools/mig-controller/pull/1359

Comment 7 mohamed 2023-11-05 11:30:10 UTC

Verified,

The migraion with custom CA set to the mig storage is working as expected

Comment 12 errata-xmlrpc 2023-11-15 01:25:53 UTC

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