Bug 2047829 - [MTC] Discovery service looking for migration CRDs on the legacy operator installed cluster
Summary: [MTC] Discovery service looking for migration CRDs on the legacy operator ins...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Operator
Version: 1.7.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 1.7.0
Assignee: Pranav Gaikwad
QA Contact: Xin jiang
Steve Goodman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-28 16:19 UTC by Prasad Joshi
Modified: 2022-03-24 06:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-24 06:32:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor mig-controller pull 1261 0 None Draft Bug 2047829: migration resources inventoried only on host cluster. 2022-01-28 20:16:20 UTC
Red Hat Product Errata RHBA-2022:1043 0 None None None 2022-03-24 06:32:59 UTC

Comment 4 Prasad Joshi 2022-02-02 07:27:44 UTC 
Verified with MTC 1.7.0
SOURCE CLUSTER: AWS 4.5 MTC 1.7.0 (Legacy Operator)
TARGET CLUSTER:  AWS 4.9 MTC 1.7.0

$ oc get pods -n openshift-migration migration-operator-7986c67bcb-hzqsd -o yaml
image: brew.registry.redhat.io/rh-osbs/rhmtc-openshift-migration-legacy-operator:v1.7.0-26


Triggered few migrations from UI, Namespace discovery is working fine now.

Moving this to Verified status.
Comment 6 errata-xmlrpc 2022-03-24 06:32:50 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.7.0 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-2022:1043
Note You need to log in before you can comment on or make changes to this bug.