Bug 1890183 - [External] ocs-operator logs are filled with "failed to reconcile metrics exporter"
Summary: [External] ocs-operator logs are filled with "failed to reconcile metrics exp...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 4.6.0
Assignee: Jose A. Rivera
QA Contact: Rachael
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-21 15:29 UTC by Rachael
Modified: 2021-06-01 08:47 UTC (History)
5 users (show)

Fixed In Version: 4.6.0-148.ci
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-17 06:25:20 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ocs-operator pull 865 0 None closed [release-4.6] Bug 1890183: Resolve errors reconciling metrics-exporter 2021-01-27 11:55:20 UTC
Red Hat Product Errata RHSA-2020:5605 0 None None None 2020-12-17 06:25:41 UTC

Description Rachael 2020-10-21 15:29:48 UTC
Description of problem:

In OCS 4.6 external mode cluster, the ocs-operator logs are filled with the following error messages

{"level":"error","ts":"2020-10-21T15:23:25.280Z","logger":"controller_storagecluster","msg":"failed to reconcile metrics exporter","Request.Namespace":"openshift-storage","Request.Name":"ocs-external-storagecluster","error":"failed to update service openshift-storage/ocs-metrics-exporter. Service \"ocs-metrics-exporter\" is invalid: spec.clusterIP: Invalid value: \"\": field is immutable","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/remote-source/app/vendor/github.com/go-logr/zapr/zapr.go:128\ngithub.com/openshift/ocs-operator/pkg/controller/storagecluster.(*ReconcileStorageCluster).Reconcile\n\t/remote-source/app/pkg/controller/storagecluster/reconcile.go:351\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:256\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:232\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:211\nk8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/remote-source/app/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:152\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/remote-source/app/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:153\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/remote-source/app/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88"}


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

$ oc get csv
NAME                         DISPLAY                       VERSION        REPLACES              PHASE
ocs-operator.v4.6.0-137.ci   OpenShift Container Storage   4.6.0-137.ci   ocs-operator.v4.5.1   Succeeded

OCP version : 4.6.0-0.nightly-2020-10-20-172149

How reproducible:
2/2

Steps to Reproduce:


Actual results:


Expected results:


Additional info:
These error messages were seen on both upgraded clusters and new deployments of OCS 4.6 external mode

Comment 3 Jose A. Rivera 2020-10-23 14:38:29 UTC
A fix is already in the works: https://github.com/openshift/ocs-operator/pull/814

Comment 6 Jose A. Rivera 2020-10-26 16:25:52 UTC
Backport PR merged: https://github.com/openshift/ocs-operator/pull/865

Comment 10 errata-xmlrpc 2020-12-17 06:25:20 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 (Moderate: Red Hat OpenShift Container Storage 4.6.0 security, bug fix, enhancement 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/RHSA-2020:5605


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