Bug 2310208 - Possibility of mismatched client-console deployments in client-operator bundles
Summary: Possibility of mismatched client-console deployments in client-operator bundles
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ocs-client-operator
Version: 4.17
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: ---
Assignee: Leela Venkaiah Gangavarapu
QA Contact: Neha Berry
URL:
Whiteboard: isf-provider
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-09-05 12:31 UTC by Leela Venkaiah Gangavarapu
Modified: 2024-10-14 10:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OCSBZM-9020 0 None None None 2024-09-05 12:32:08 UTC

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