Bug 1891666 - Should use OCP rather than OKD in description
Summary: Should use OCP rather than OKD in description
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.7.0
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard: logging-core, logging-exploration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-27 02:26 UTC by Anping Li
Modified: 2021-02-24 11:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 11:21:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift elasticsearch-operator pull 552 0 None closed Bug 1891666: LOG-900: Updating hacking docs and csv to be more up-to-date 2021-02-19 10:32:58 UTC
Red Hat Product Errata RHBA-2021:0652 0 None None None 2021-02-24 11:22:12 UTC

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


Note You need to log in before you can comment on or make changes to this bug.