Bug 1891666

Summary: Should use OCP rather than OKD in description
Product: OpenShift Container Platform Reporter: Anping Li <anli>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.6CC: aos-bugs, periklis
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: logging-core, logging-exploration
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 11:21:19 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 Anping Li 2020-10-27 02:26:20 UTC
Description of problem:
The words 'OKD cluster' is used in the features description the Webconsole->OperatorHub-> elasticsearch-operator. It should be OCP.  

The Elasticsearch Operator for OKD provides a means for configuring and managing an Elasticsearch cluster for use in tracing and cluster logging. This operator only supports OKD Cluster Logging and Jaeger. It is tightly coupled to each and is not currently capable of being used as a general purpose manager of Elasticsearch clusters running on OKD.


Version-Release number of selected component (if applicable):
elasticsearch-operator.4.6.0-202010261040.p0

How Reproducible:
Always

Steps to Reproduce:
1. check the install button on the console
2. Check the feature description

Comment 2 Anping Li 2020-11-03 08:26:39 UTC
Verified on elasticsearch-operator.4.7.0-202011030448.p0

Comment 7 errata-xmlrpc 2021-02-24 11:21:19 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 (Errata Advisory for Openshift Logging 5.0.0), 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-2021:0652