Bug 1889374

Summary:	Kiali feature won't work on fresh 4.6 cluster
Product:	OpenShift Container Platform	Reporter:	Jaivardhan Kumar <jakumar>
Component:	Dev Console	Assignee:	cvogt
Status:	CLOSED NOTABUG	QA Contact:	Gajanan More <gamore>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.6	CC:	aballant, aos-bugs, nmukherj, viraj
Target Milestone:	---
Target Release:	4.7.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:	2021-01-11 04: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 Jaivardhan Kumar 2020-10-19 13:54:21 UTC

Description of problem: The availability of Kiali features in ODC are dependent on the availability of the Elastic search operator as Service Mesh operator depends on it. Currently this operator is not available on the fresh installation of OCP 4.6. However these features, are available when you upgrade OCP from a previous version to the latest.


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


How reproducible: Always


Steps to Reproduce:
1. Install Service Mesh operator
2. Create a name space and add some workloads
3. In topology can't see link to kiali

Actual results: Can't see Kiali link on topology


Expected results: Should see kiali link in topology


Additional info:

Comment 1 Vikram Raj 2020-11-02 14:48:41 UTC

I verified the Kiali feature by installing Elastic Search, Jaeger, Kiali, and Red Hat OpenShift Service Mesh operators on 4.6 cluster and it is working as expected.

Comment 3 Jaivardhan Kumar 2021-01-11 04:17:01 UTC

Marking it as closed as this is not a bug on ODC side as the fix was associated with operator not in ODC and this feature was dependent on it.