Bug 2103674

Summary: Remove update channel release-v2.3.0
Product: Migration Toolkit for Virtualization Reporter: Maayan Hadasi <mguetta>
Component: OperatorAssignee: Arik <ahadas>
Status: CLOSED MIGRATED QA Contact: Maayan Hadasi <mguetta>
Severity: high Docs Contact: Richard Hoch <rhoch>
Priority: unspecified    
Version: 2.3.0CC: ahadas, istein, joschrod, mnecas
Target Milestone: ---   
Target Release: Future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-03 09:14:45 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
install_operator
none
about_mtv none

Description Maayan Hadasi 2022-07-04 13:14:22 UTC 
Description of problem:
When installing MTV GA via OCP UI and selecting release-v2.3.0 as the Update channel, *MTV 2.3.1 GA* is installed.
Please see attached screenshots

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

How reproducible:
100%

Expected results:
MTV 2.3.0 GA should be installed

Additional info:
Comment 1 Maayan Hadasi 2022-07-04 13:14:53 UTC 
Created attachment 1894509 [details]
install_operator
Comment 2 Maayan Hadasi 2022-07-04 13:15:18 UTC 
Created attachment 1894510 [details]
about_mtv
Comment 3 Arik 2023-01-02 14:42:14 UTC 
Maayan, why do we expect to have both release-v2.3 and release-v2.3.0?
Comment 4 Maayan Hadasi 2023-01-03 06:35:03 UTC 
(In reply to Arik from comment #3)
> Maayan, why do we expect to have both release-v2.3 and release-v2.3.0?

Hi Arik,
These were available options as "Update channel" when I opened this bug.
Now, *assuming* that release-v2.3.0 option was removed, it makes sense to close the issue
Comment 5 Arik 2023-01-03 09:13:57 UTC 
(In reply to Maayan Hadasi from comment #4)
> (In reply to Arik from comment #3)
> > Maayan, why do we expect to have both release-v2.3 and release-v2.3.0?
> 
> Hi Arik,
> These were available options as "Update channel" when I opened this bug.
> Now, *assuming* that release-v2.3.0 option was removed, it makes sense to
> close the issue

Thanks Maayan. The release-v2.3.0 wasn't removed but I think that's the right resolution for this bz, to remove it