Bug 2310208

Summary:	Possibility of mismatched client-console deployments in client-operator bundles
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Leela Venkaiah Gangavarapu <lgangava>
Component:	ocs-client-operator	Assignee:	Leela Venkaiah Gangavarapu <lgangava>
Status:	ASSIGNED ---	QA Contact:	Neha Berry <nberry>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.17	CC:	muagarwa, odf-bz-bot, omitrani, rohgupta
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	isf-provider
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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:

Description Leela Venkaiah Gangavarapu 2024-09-05 12:31:18 UTC

Description of problem:
1. client-op can be deployed on all supported OCP versions from 4.14, i.e, client-op 4.16 can be run on ocp 4.14 and this creates a mismatch of client-console part of client-op 4.16 to run on ocp 4.14 which is untested
2. currently client-op employs a mechanism for selecting appropriate CSI versions based on ocp and this needs to be extended for deploying & configuring client-console based on ocp versions

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

How reproducible:
always

Steps to Reproduce:
1. deploy client-op 4.17 on ocp 4.16 (typical for hcp)

Actual results:
client-console that matches client-op version is deployed

Expected results:
client-console that matches platform/ocp version should be deployed

Additional info: