Bug 1937290 - MTC upgrade from 1.3.2 to 1.4.2 is stuck due to the old version cannot update
Summary: MTC upgrade from 1.3.2 to 1.4.2 is stuck due to the old version cannot update
Keywords:
Status: CLOSED DUPLICATE of bug 1937295
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Operator
Version: 1.4.2
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 1.3.z
Assignee: John Matthews
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-10 09:57 UTC by Xin jiang
Modified: 2021-03-10 13:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-10 13:42:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
upgrade (55.56 KB, image/png)
2021-03-10 09:57 UTC, Xin jiang
no flags Details

Description Xin jiang 2021-03-10 09:57:00 UTC
Created attachment 1762241 [details]
upgrade

Description of problem:
I installed MTC 1.3.2 version with stage images by selecting channel "release-v1.3" on OCP 4.7. And then selecting channel  "release-v1.4", the Operator upgrade is stuck and the older version is showing up a warning message:

Cannot update
Catalogsource Was removed

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

How reproducible:
Always

Steps to Reproduce:
1. installed MTC 1.3.2 version with stage images by selecting channel "release-v1.3" on OCP 4.7
2. Create MigController instance 
3. selecting channel "release-v1.4" and waiting for it to upgrade to 1.4.2

Actual results:
The upgrade is stuck. the older version is showing up a warning message:
"
Cannot update
Catalogsource Was removed
"

Expected results:
It should be automatically upgraded to 1.4.2

Additional info:

Comment 1 Xin jiang 2021-03-10 13:42:34 UTC

*** This bug has been marked as a duplicate of bug 1937295 ***


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