Bug 2208291

Summary:	ODF 4.12 is shown on UI while installing ODF 4.13 over OCP 4.13
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Aman Agrawal <amagrawa>
Component:	build	Assignee:	Boris Ranto <branto>
Status:	CLOSED WONTFIX	QA Contact:	Petr Balogh <pbalogh>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.13	CC:	ammahapa, branto, muagarwa, nigoyal, ocs-bugs, odf-bz-bot, skatiyar, uchapaga
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
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-06-02 05:21:48 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:

Comment 2 Sanjal Katiyar 2023-05-22 12:15:59 UTC

UI (OCP) reads this info from the PackageManifest, maybe PackageManifest did not had "currentCSV: odf-operator.v4.13.0-201.stable" field corresponding to its channels list.
Moving to odf operator for now (as am not sure if it is build issue or operator).

Comment 3 Mudit Agarwal 2023-05-23 06:23:53 UTC

Starting with build component.

Aman, can you pls check if this is happening with the latest builds too.

Comment 4 Boris Ranto 2023-05-23 07:56:42 UTC

There is no 4.12 string in odf-operator CSV in 4.13.0 so this value is not coming from there. My guess would be that it takes OCP some time to reconcile the data after you patch the catalog source. Does this still happen if you wait some time before installing ODF after patching the catalog source? What does is show when you pick the version to install?

Comment 8 Boris Ranto 2023-05-31 08:48:52 UTC

OK, this screencast better describes the situation. I can't say I have an idea on what is going on.

@uchapaga @nigoyal Any idea what might be going on here?

Comment 9 Nitin Goyal 2023-05-31 09:07:26 UTC

To me, it looks like more of an OCP console bug. Can we pls create a Jira ticket for this in the OCP? console might be making some queries to get the version that has some bugs in it.

Comment 10 umanga 2023-05-31 12:32:28 UTC

This could be an OCP console/OLM API issue.
If this happens only when using internal catalog images, there could be something wrong with how it gets built.
Since we don't release these catalogs, probably not worth fixing or trying to fix it.

Comment 11 Boris Ranto 2023-06-02 05:21:48 UTC

As per the comments above, closing as WONTFIX. We can try to create an OCP JIRA ticket for the same.