Bug 1909183

Summary: Problems with the default version when installing MTC 1.4.0 using OLM.
Product: Migration Toolkit for Containers Reporter: Sergio <sregidor>
Component: OperatorAssignee: Shawn Hurley <shurley>
Status: CLOSED DUPLICATE QA Contact: Xin jiang <xjiang>
Severity: medium Docs Contact: Avital Pinnick <apinnick>
Priority: medium    
Version: 1.4.0CC: chezhang, ernelson, jmontleo, rpattath, shurley, whu, xjiang
Target Milestone: ---   
Target Release: 1.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-07 18:45:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
default version screenshot
none
install disabled button screenshot none

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 ***