Bug 1790564 - [RFE] Don't fail migrations if internal registry is not present on src cluster
Summary: [RFE] Don't fail migrations if internal registry is not present on src cluster
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Migration Tooling
Version: 4.2.z
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.4.0
Assignee: Scott Seago
QA Contact: Xin jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-13 16:04 UTC by Scott Seago
Modified: 2020-05-28 11:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-28 11:09:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:2326 0 None None None 2020-05-28 11:10:20 UTC

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


Note You need to log in before you can comment on or make changes to this bug.