Bug 1790564

Summary:	[RFE] Don't fail migrations if internal registry is not present on src cluster
Product:	OpenShift Container Platform	Reporter:	Scott Seago <sseago>
Component:	Migration Tooling	Assignee:	Scott Seago <sseago>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.2.z	CC:	dymurray, jmatthew, sregidor
Target Milestone:	---
Target Release:	4.4.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:	2020-05-28 11:09:55 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 Scott Seago 2020-01-13 16:04:22 UTC

Description of problem:
Currently, if the internal registry for the source cluster is not found (or does not exist), the migration fails. In some environments, the internal registry is not used, so instead of failing with no registry, we should just disable the internal image copy feature.

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


How reproducible: Always


Steps to Reproduce:
1. Use a source cluster with no internal registry
2. Create a migplan for a namespace in this cluster
3. Migrate

Actual results:
Backup fails with error related to the internal registry: 'services \"docker-registry\" not found'

Expected results:
Migration succeeds.

Additional info:

Comment 1 Scott Seago 2020-04-10 16:01:10 UTC

fix PR is here: https://github.com/konveyor/openshift-migration-plugin/pull/59

Comment 5 Sergio 2020-05-11 11:58:32 UTC

Verified using CAM 1.2 stage

3.11 -> 4.2. Internal registry was disabled in both clusters, plus additionally the docker-registry service was removed from 3.11 cluster. The migration didn't fail.

Comment 7 errata-xmlrpc 2020-05-28 11:09:55 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, 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/RHEA-2020:2326