Bug 1909183 - Problems with the default version when installing MTC 1.4.0 using OLM.
Summary: Problems with the default version when installing MTC 1.4.0 using OLM.
Keywords:
Status: CLOSED DUPLICATE of bug 1885425
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Operator
Version: 1.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 1.4.0
Assignee: Shawn Hurley
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-18 14:29 UTC by Sergio
Modified: 2021-01-07 18:45 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-07 18:45:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
default version screenshot (143.88 KB, image/png)
2020-12-18 14:29 UTC, Sergio
no flags Details
install disabled button screenshot (77.58 KB, image/png)
2020-12-18 14:30 UTC, Sergio
no flags Details

Description Sergio 2020-12-18 14:29:29 UTC
Created attachment 1740303 [details]
default version screenshot

Description of problem:
When we install MTC 1.4.0 using OLM, the default version to install is 1.2.5. The default version should be 1.4.0. Plus, when we select 1.4.0 version and "Operator recommended namespace", the "Install" button remains disabled. We are forced to select "Pick an existing namespace" and create the namespace manually.

Version-Release number of selected component (if applicable):
MTC 1.4.0 stage
OCP 4.5


How reproducible:
Always

Steps to Reproduce:
1. Install MTC 1.4.0 from stage using OLM

Actual results:
The default version is 1.2.5
The "Operator recommended namespace" is not working properly.

Expected results:
The default version should be 1.4.0 and we should be able to let the OLM create the recommended namespace.

Additional info:

Comment 1 Sergio 2020-12-18 14:30:31 UTC
Created attachment 1740304 [details]
install disabled button screenshot

Comment 5 Shawn Hurley 2021-01-07 18:45:19 UTC

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


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