Bug 2001089

Summary:	Direct volume migration fails because of missing CA path configuration
Product:	Migration Toolkit for Containers	Reporter:	Dylan Murray <dymurray>
Component:	Controller	Assignee:	Pranav Gaikwad <pgaikwad>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	urgent	Docs Contact:	Avital Pinnick <apinnick>
Priority:	urgent
Version:	1.6.0	CC:	ernelson, rjohnson, sregidor, xjiang
Target Milestone:	---
Target Release:	1.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-09-29 14:35: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:

Description Dylan Murray 2021-09-03 18:35:37 UTC

Description of problem:
Direct volume migration is failing due to misconfiguration of stunnel with a recent change that was introduced in crane-lib.

Here is the error in the stunnel pod:

[ ] Clients allowed=512000
[.] stunnel 5.56 on x86_64-redhat-linux-gnu platform
[.] Compiled/running with OpenSSL 1.1.1g FIPS  21 Apr 2020
[.] Threading:PTHREAD Sockets:POLL,IPv6 TLS:ENGINE,FIPS,OCSP,PSK,SNI
[ ] errno: (*__errno_location ())
[.] Reading configuration from file /etc/stunnel/stunnel.conf
[.] UTF-8 byte order mark not detected
[.] FIPS mode disabled
[ ] Compression disabled
[ ] No PRNG seeding was required
[ ] Initializing service [rsync]
[!] Service [rsync]: Either "CAfile" or "CApath" has to be configured
[ ] Deallocating section defaults

Version-Release number of selected component (if applicable):
1.6.0

How reproducible:

100%

Steps to Reproduce:
1. Run migration with DVM enabled
2.
3.

Actual results:
DVM fails with above error in stunnel container

Expected results:
DVM succeeds

Additional info:

Comment 1 Xin jiang 2021-09-06 08:22:21 UTC

*** Bug 2001412 has been marked as a duplicate of this bug. ***

Comment 5 Sergio 2021-09-08 11:17:39 UTC

Verfied using:
SOURCE CLUSTER: AWS OCP 3.11 (MTC 1.5.1) NFS
TARGET CLUSTER: AWS OCP 4.9 (MTC 1.6.0) OCS4

openshift-migration-rhel8-operator@sha256:ef00e934ed578a4acb429f8710284d10acf2cf98f38a2b2268bbea8b5fd7139c
    - name: MIG_CONTROLLER_REPO
      value: openshift-migration-controller-rhel8@sha256
    - name: MIG_CONTROLLER_TAG
      value: 27f465b2cd38cee37af5c3d0fd745676086fe0391e3c459d4df18dd3a12e7051
    - name: MIG_UI_REPO
      value: openshift-migration-ui-rhel8@sha256
    - name: MIG_UI_TAG

DVM migrations could be executed without problems

Moved to VERIFIED.

Comment 7 errata-xmlrpc 2021-09-29 14:35: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.6.0 security & bugfix 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-2021:3694