Bug 1833297

Summary:	Remove CephClient from the UI of OCS Operator
Product:	[Red Hat Storage] Red Hat OpenShift Container Storage	Reporter:	Neha Berry <nberry>
Component:	ocs-operator	Assignee:	umanga <uchapaga>
Status:	CLOSED ERRATA	QA Contact:	Yosi Ben Shimon <ybenshim>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	ebenahar, jarrpa, madam, ocs-bugs, sostapov
Target Milestone:	---
Target Release:	OCS 4.5.0
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:	2020-09-15 10:17:01 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:

Description Neha Berry 2020-05-08 10:56:03 UTC

Description of problem (please be detailed as possible and provide log
snippests):
--------------------------------------------------------------------
This bug is spinned off to track the removal of CephClient CR from OCS Operaotr UI page ( see Bug 1772084#c29)

It is currently listed as [Internal]CephClient and the "Status" also keeps reflecting as Unknown. If not needed, we can rather remove it entirely from being displayed.



Version of all relevant components (if applicable):
=======================================================

OCS 4.4 all rc builds, OCS 4.3 (see https://bugzilla.redhat.com/show_bug.cgi?id=1772084#c18)


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
===========================================================
No

Is there any workaround available to the best of your knowledge?
====================================================================
No

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
=============================================================================
2

Can this issue reproducible?
=================================
Yes

Can this issue reproduce from the UI?
==========================================
Yes

If this is a regression, please provide more details to justify this:
==========================================================================
No. It was present in 4.3 and 4.4 both

Steps to Reproduce:
=========================

1. Create an OCP 4.4 cluster with 3 or more Worker nodes
2. Using ocs-ci or UI, install the OCS Operator OCS 4.4 and install OCS
3. Check the Installed Operators->All Instances . CephClient CR is listed and Status is Unknown
4. Check the Installed Operators --> ocs-operator.v0.0.233--> different tabs. CephClient CR is listed and Status is Unknown



Actual results:
====================
CephClient CR is listed in OCS 4.4 as [Internal] 

Expected results:
========================

As per Bug 1772084#c29, it can be removed.

Comment 6 Jose A. Rivera 2020-05-08 15:11:30 UTC

There is nothing about this that should mark it a blocker for OCS 4.4, given where we are in the release cycle, especially if it's already fixed for OCS 4.5. It's nowhere near critical enough to warrant even backporting in a z-stream release. I'm moving this to OCS 4.5 and marking it as MODIFIED since the fix is already in place.

Comment 7 Elad 2020-05-08 19:48:38 UTC

OCS docs do not mention anything about CephClient. If there is no use case for this CR, I tend to agree this is not a blocker for 4.4.

Comment 13 Yosi Ben Shimon 2020-06-21 11:54:27 UTC

Tested on:
OpenShift Version
4.5.0-0.nightly-2020-06-20-194346

OCS version: 4.5.0

The [internal] CephClient has been removed from:
- Installed Operators -> All Instances
- Installed Operators -> ocs-storagecluster--> different tabs.

Moving to VERIFIED

Comment 15 errata-xmlrpc 2020-09-15 10:17:01 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenShift Container Storage 4.5.0 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3754