Bug 2007375

Summary:	MigCluster CR remains in "unready" state and source registry is inaccessible after temporary shutdown of source cluster
Product:	Migration Toolkit for Containers	Reporter:	Erik Nelson <ernelson>
Component:	Controller	Assignee:	Scott Seago <sseago>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	low	Docs Contact:	Avital Pinnick <apinnick>
Priority:	low
Version:	1.5.0	CC:	apinnick, ernelson, jmatthew, rjohnson, sseago, ssingla, xjiang
Target Milestone:	---
Target Release:	1.6.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2006842	Environment:
Last Closed:	2021-10-28 09:48:01 UTC	Type:	---
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:	2006842, 2008946
Bug Blocks:

Description Erik Nelson 2021-09-23 17:21:36 UTC

+++ This bug was initially created as a clone of Bug #2006842 +++

Description of problem:

As part of working MTC 1.5 lab updates we ran into situation that the source OCP 3 cluster was shutdown on us.  When this happened the MigCluster source went into an unready state as expected.

We brought the source cluster back up and saw the MigCluster change state to show that it could not communicate with the source API server, yet the registry remained as unreachable.

We waited ~15+ minutes and didn't see the MigCluster change, was using the UI and clicked Check Connection multiple times, it would look like it was trying to connect and come back to say it failed due to the registry.

Eventually we got it working by:
1) From the UI, update the MigCluster and delete the registry URL
2) Save the MigCluster
3) See the MigCluster go healthy
4) Edit the MigCluster, enter the same registry URL back in
5) Save the MigCluster, see it go healthy

It looks like we may have a bug somewhere to detect when a source cluster goes away and comes back, the logic for the docker-registry readiness is not correct.  




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

MTC 1.5

How reproducible:
Unsure, but I would suspect reproducible

Steps to Reproduce:
1. Provision a cluster pair via our lab system (opentlc)
2. Setup and perform a migration of a sample app to prove things are working correctly, ensure you add the source docker-registry so you can test a Direct Image Migration workflow
3. From opentlc, temporarily shutdown the source cluster
4. See the MigCluster go to unready
5. Turn the source cluster back on and observe the MigCluster

Comment 11 errata-xmlrpc 2021-10-28 09:48:01 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 (Migration Toolkit for Containers (MTC) 1.6.1 release advisory), 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/RHBA-2021:4023