Bug 1999381 - MigPlan custom resource displays "Stage completed with warnings" status after successful migration
Summary: MigPlan custom resource displays "Stage completed with warnings" status after...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: UI
Version: 1.6.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 1.6.0
Assignee: Ian
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-31 04:30 UTC by Xin jiang
Modified: 2021-09-29 14:35 UTC (History)
4 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor mig-ui pull 1308 0 None None None 2021-09-02 16:00:49 UTC
Github konveyor mig-ui pull 1310 0 None None None 2021-09-03 13:44:36 UTC
Red Hat Product Errata RHSA-2021:3694 0 None None None 2021-09-29 14:35:46 UTC

Description Xin jiang 2021-08-31 04:30:03 UTC
Description of problem:
The previous Stage operation completed with waring. Though the last Stage completed successfully, the migplan still shows up message "Stage completed with warnings"

Version-Release number of selected component (if applicable):
MTC 1.6.0

How reproducible:
Always


Steps to Reproduce:
1. Executed Stage operation and the Stage completed with waring. For instance, the migration configuration doesn't support snapshot copy, but still select snapshot copy while creating migplan
2. Modified the migplan with filesystem copy
3. Executed Stage operation again and the Stage completed successfully

Actual results:
The migplan's last state still is showing up a warning "Stage completed with warnings"

Expected results:
The warning should be gone


Additional info:

Comment 1 Erik Nelson 2021-08-31 13:27:56 UTC
I think this is a duplicate, I recall another bug filed around this but I'm not sure if it was 1.6.0 or not. Ian does this look familiar to you? I think we closed the last one as wontfix.

Comment 2 Ian 2021-09-01 14:55:17 UTC
I can take another look today @Erik to see if there is a fix.

Comment 7 Sergio 2021-09-08 12:49:03 UTC
Verfied using:
SOURCE CLUSTER: AWS OCP 3.11 (MTC 1.5.1) NFS
TARGET CLUSTER: AWS OCP 4.9 (MTC 1.6.0) OCS4

openshift-migration-rhel8-operator@sha256:ef00e934ed578a4acb429f8710284d10acf2cf98f38a2b2268bbea8b5fd7139c
    - name: MIG_CONTROLLER_REPO
      value: openshift-migration-controller-rhel8@sha256
    - name: MIG_CONTROLLER_TAG
      value: 27f465b2cd38cee37af5c3d0fd745676086fe0391e3c459d4df18dd3a12e7051
    - name: MIG_UI_REPO
      value: openshift-migration-ui-rhel8@sha256
    - name: MIG_UI_TAG

After the successful stage migration the UI is reporting correctly "Stage succeeded" 


Moved to VERIFIED status.

Comment 9 errata-xmlrpc 2021-09-29 14:35: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 (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.