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

Bug 1869117

Summary: 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.`
Product: OpenShift Container Platform Reporter: Qiaoling Tang <qitang>
Component: LoggingAssignee: ewolinet
Status: CLOSED ERRATA QA Contact: Qiaoling Tang <qitang>
Severity: high Docs Contact:
Priority: urgent    
Version: 4.6CC: aconway, aos-bugs, ewolinet
Target Milestone: ---Keywords: Regression, TestBlocker
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: logging-exploration
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 15:09:55 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 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