This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2103674 - Remove update channel release-v2.3.0
Summary: Remove update channel release-v2.3.0
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Migration Toolkit for Virtualization
Classification: Red Hat
Component: Operator
Version: 2.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: Future
Assignee: Arik
QA Contact: Maayan Hadasi
Richard Hoch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-04 13:14 UTC by Maayan Hadasi
Modified: 2023-01-03 09:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-03 09:14:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
install_operator (76.41 KB, image/png)
2022-07-04 13:14 UTC, Maayan Hadasi 		no flags Details
about_mtv (354.33 KB, image/png)
2022-07-04 13:15 UTC, Maayan Hadasi 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   MTV-458 0 None None None 2023-01-03 09:14:44 UTC

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
Note You need to log in before you can comment on or make changes to this bug.