Bug 1936549 - MTC version mismatch not reported in the MigPlan when the migration controller is deployed on the source cluster
Summary: MTC version mismatch not reported in the MigPlan when the migration controlle...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: General
Version: 1.4.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 1.4.2
Assignee: John Matthews
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-08 17:49 UTC by Sergio
Modified: 2021-03-15 08:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-15 08:15:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor mig-controller pull 990 0 None open Bug 1936549: Fix problem with dest cluster configmap missing not triggering version warning 2021-03-08 17:51:27 UTC
Github konveyor mig-controller pull 991 0 None open Bug 1936549: Cherry-pick: BZ 1936549 fix (#990) 2021-03-08 17:55:20 UTC
Red Hat Product Errata RHBA-2021:0814 0 None None None 2021-03-15 08:15:46 UTC

Description Sergio 2021-03-08 17:49:56 UTC
Description of problem:
When the migration controller is deployed in the source cluster and the remote (target) cluster has a different MTC version installed, the migration plan is not showing any warning and it should do it.

When the migration controller is deployed in the target cluster this warning is reported properly.


Version-Release number of selected component (if applicable):
MTC 1.4.2 stage.

How reproducible:
Always

Steps to Reproduce:
1. Install MTC like this

Target cluster (4.5): MTC 1.3.2
Source cluster (3.11): MTC 1.4.2 (Controller)


2. Create a namespace in the source cluster

oc new-project empty-namespace


3. Create a migration plan to migrate this namespace from source to target cluster.

Actual results:
We can see a warning in the Target cluster saying that the MTC version cannot be found
      lastTransitionTime: 2021-03-08T17:18:00Z
      message: MTC operator version lookup failed on cluster target-cluster. Key OPERATOR_VERSION
        not found in configmap openshift-migration/migration-cluster-config. Ensure
        that all clusters are running the same MTC Operator version.
      reason: VersionNotFound


But the migration plan does not show any warning once it is created.

Expected results:
The migration plan should report a warning saying that the target cluster's version cannot be found.

Additional info:
When the migration controller is deployed in the target cluster the warning is reported properly.

Comment 4 Sergio 2021-03-09 13:24:50 UTC
Verified using MTC 1.4.2, AWS OCP3.11(controller)->AWS OCP4.5

openshift-migration-rhel7-operator@sha256:9e8990d8c4b54b2d72122ac4cbe5d76ad073c44f1295b4f4128ed767de511230
    - name: MIG_CONTROLLER_REPO
      value: openshift-migration-controller-rhel8@sha256
    - name: MIG_CONTROLLER_TAG
      value: fa5481c45948eaed1a948d0f43dd122e0a94c2aec2612724fc8b2e92b190d4f5


The migration plan shows now this warning, as expected:
    - category: Warn
      lastTransitionTime: "2021-03-09T13:20:22Z"
      message: Cluster operator versions do not match. Source, destination, and host clusters must all have the same MTC operator version.
      reason: Conflict
      status: "True"
      type: ClusterVersionMismatch


Moved to VERIFIED status.

Comment 8 errata-xmlrpc 2021-03-15 08:15:38 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) image release advisory 1.4.2), 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:0814


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