Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1913464

Summary:	Elasticsearch Operator does not report on csv success
Product:	OpenShift Container Platform	Reporter:	ewolinet
Component:	Logging	Assignee:	ewolinet
Status:	CLOSED ERRATA	QA Contact:	Qiaoling Tang <qitang>
Severity:	low	Docs Contact:	Rolfe Dlugy-Hegwer <rdlugyhe>
Priority:	medium
Version:	4.7	CC:	aos-bugs, periklis, rdlugyhe
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	logging-exploration
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	[discrete] [id="ocp-4-7-es-csv-success"] // https://bugzilla.redhat.com/show_bug.cgi?id=1913464 ==== Elasticsearch Operator reports on CSV success The current release adds reporting metrics to indicate that installing or upgrading the Elasticsearch Operator ClusterServiceVersion (CSV) was successful. Previously, there was no way to determine, or generate an alert, if the CSV installation or upgrade for the Elasticsearch Operator had failed. Now, an alert has been created and is provided as part of installing the Elasticsearch Operator.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 11:22:33 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 ewolinet 2021-01-06 20:26:55 UTC

Description of problem:
Currently there is no way to determine if the elasticsearch operator csv was successfully updated/installed.

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

How reproducible:
Always

Actual results:
No alerts on whether or not csv was successful

Expected results:
Alerts available

Comment 3 Qiaoling Tang 2021-01-08 08:17:20 UTC

Testing steps:
1. deploy logging
2. check the elasticsearch-operator CSV status, it's Succeeded
3. check alert in openshift console, the alert `ElasticsearchOperatorCSVNotSuccessful` is created but not pending/firing
4. make the EO pod pending, e.g.: add nodeSelector to the elasticsearch-operator CSV to make the EO pod couldn't be scheduled to any nodes in the cluster
5. check the elasticsearch-operator CSV status, it's Installing
6. check alert in openshift console again, the alert `ElasticsearchOperatorCSVNotSuccessful` becomes pending, 10 minutes later, it becomes firing

CSV version: elasticsearch-operator.4.7.0-202101070834.p0

Move this BZ to VERIFIED.

Comment 5 ewolinet 2021-02-08 18:00:19 UTC

Replaced "Metering" with "Elasticsearch"

Comment 8 errata-xmlrpc 2021-02-24 11:22:33 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