Bug 1869117 - Infra/app/audit indices couldn't be created in default ES due to `Failed to reconcile PrometheusRules for Elasticsearch cluster: failed to build prometheus rule.`
Summary: Infra/app/audit indices couldn't be created in default ES due to `Failed to r...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.6
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: 4.6.0
Assignee: ewolinet
QA Contact: Qiaoling Tang
URL:
Whiteboard: logging-exploration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-17 01:53 UTC by Qiaoling Tang
Modified: 2020-10-27 15:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 15:09:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift elasticsearch-operator pull 458 0 None closed Bug 1869117: fixing alerts formatting, add unit test to validate 2020-10-28 10:32:11 UTC
Red Hat Product Errata RHBA-2020:4198 0 None None None 2020-10-27 15:10:11 UTC

Description Qiaoling Tang 2020-08-17 01:53:14 UTC
Description of problem:
Deploy logging stack, the EO can't create prometheusrule for elasticsearch:

{"level":"error","ts":1597628275.855222,"logger":"controller-runtime.controller","msg":"Reconciler error","controller":"elasticsearch-controller","request":"openshift-logging/elasticsearch","error":"Failed to reconcile PrometheusRules for Elasticsearch cluster: failed to build prometheus rule: error converting YAML to JSON: yaml: line 68: did not find expected key","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/src/github.com/openshift/elasticsearch-operator/vendor/github.com/go-logr/zapr/zapr.go:128\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/src/github.com/openshift/elasticsearch-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:258\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/src/github.com/openshift/elasticsearch-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:232\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/go/src/github.com/openshift/elasticsearch-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:211\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1\n\t/go/src/github.com/openshift/elasticsearch-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:155\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil\n\t/go/src/github.com/openshift/elasticsearch-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:156\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/go/src/github.com/openshift/elasticsearch-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/go/src/github.com/openshift/elasticsearch-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:90"}

Besides, the delete/rollover cronjobs are not created, the ES couldn't receive logs since the app/infra indices are not created in the ES cluster.

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

How reproducible:
Always

Steps to Reproduce:
1. deploy CLO and EO
2. create clusterlogging instance
3.

Actual results:


Expected results:


Additional info:

Comment 1 Qiaoling Tang 2020-08-17 06:03:52 UTC
Because the EO failed to create the prometheusrule/elasticsearch-prometheus-rules, it doesn't do the steps to create the elasticsearch-delete-xxx/elasticsearch-rollover-xxx cron jobs, all the infra and app logs are not received.

Comment 5 Qiaoling Tang 2020-08-24 07:39:25 UTC
Verified with elasticsearch-operator.4.6.0-202008202200.p0

Comment 7 errata-xmlrpc 2020-10-27 15:09:55 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 (OpenShift Container Platform 4.6.1 extras 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:4198


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