Bug 2004601 - Migration plan status on "Migration plans" page is "Ready" after migration completed with warnings
Summary: Migration plan status on "Migration plans" page is "Ready" after migration co...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: UI
Version: 1.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 1.6.0
Assignee: John Matthews
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-15 16:14 UTC by Sergio
Modified: 2021-09-29 14:36 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-29 14:36:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor mig-ui pull 1330 0 None open Bug 2004601: Update plan status text for cutover with warnings 2021-09-15 16:34:45 UTC
Github konveyor mig-ui pull 1331 0 None open Bug 2004601: Update plan status text for cutover with warnings (#1330) 2021-09-15 16:40:11 UTC
Red Hat Product Errata RHSA-2021:3694 0 None None None 2021-09-29 14:36:26 UTC

Description Sergio 2021-09-15 16:14:11 UTC 
Description of problem:
When the migration plan is executed with warnings the status is reported as "Ready" with a warning icon next to the text. The right status should say that the migration was executed with warnings, and not that the migration is ready.

Version-Release number of selected component (if applicable):
SOURCE CLUSTER: AWS 3.11 (MTC 1.5.1) 
TARGET CLUSTER: ROKS 4.7 (MTC 1.6.0) (CONTROLLER + UI)
REPLICATION REPOSITORY: AWS S3

How reproducible:
Always

Steps to Reproduce:
1. I source cluster deploy an application with a PVC

oc new-project bz-test
oc new-app django-psql-persistent

2. Configure a wrong option for rsync in the migrationcontroller resource

oc edit migrationcontroller

  spec:
    rsync_opt_extras: "--fake"


3. Create a migration plan to migrate the bz-test namespace created in step1, use DIM + DVM

4. Execute the migration

Actual results:
The migration is executed with warnings, but the status in the migplan is reported as "Ready" with a warning icon beside the text.

Expected results:
The status should report that there were warnings in the migration execution, and it should not be "Ready" status.

Additional info:
Comment 5 Sergio 2021-09-16 12:56:10 UTC 
Verified using:
TARGET CLUSTER: AWS 4.9 (MTC 1.6.0) (CONTROLLER + UI)
SOURCE CLUSTER: AWS 3.11 (MTC 1.5.1)
REPLICATION REPOSITORY: AWS S3

openshift-migration-rhel8-operator@sha256:a82ed90172838ed4f9e33a8c72fee584bdeb8773b9b580c11c36f4e575c0e6da
   - name: MIG_CONTROLLER_REPO
      value: openshift-migration-controller-rhel8@sha256
    - name: MIG_CONTROLLER_TAG
      value: 3b5efa9c8197fe0313a2ab7eb184d135ba9749c9a4f0d15a6abb11c0d18b9194
    - name: MIG_UI_REPO
      value: openshift-migration-ui-rhel8@sha256
    - name: MIG_UI_TAG
      value: 854fc0192c4494e2a555f0a8b984b9d84244f77ccb75bcb72529936e24e5211a


The status now is "Migration completed with warnings".

Moved to VERIFIED.
Comment 7 errata-xmlrpc 2021-09-29 14:36:19 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 (Moderate: Migration Toolkit for Containers (MTC) 1.6.0 security & bugfix update), 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/RHSA-2021:3694
Note You need to log in before you can comment on or make changes to this bug.