failed to create or get service for metrics about elasticsearch-operator HOT 7 CLOSED

Hi, i get it too, there is a way that i can handle this problem for now?
I deployed it with the csv yaml in the manifest directory

from elasticsearch-operator.

Starting the ElasticSearch operator on OpenShift, we would find the following warning:

# oc logs -f elasticsearch-operator-5d4b85bcf8-65cb9
...
{"level":"info","ts":1574348719.3720665,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"elasticsearch-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1574348719.5793352,"logger":"cmd","msg":"failed to create or get service for metrics: services \"elasticsearch-operator\" is forbidden: cannot set blockOwnerDeletion if an ownerReference refers to a resource you can't set finalizers on: , <nil>"}
...

Looks like a warning, though could be worth fixing. Couldn't figure out what's wrong: I don't have an elasticsearch-operator service yet. Tried to create it, with then without an ownerReference to my operator deployment.

Source image for the ElasticSearch operator pod: registry.redhat.io/openshift4/ose-elasticsearch-operator@sha256:69968bc98d29773b89ba9b3c3c5b1fc44d8df5226934683e3029ae14f4829fab

How did you deploy the operator?

from elasticsearch-operator.

Using OCP (4.2) OperatorHub, following instructions deploying OCP logging stack -- https://docs.openshift.com/container-platform/4.2/logging/cluster-logging-deploying.html, clicking the console, ... I'm not sure what's going on under the hood: if you want me to dump objects, let me know what you're looking for.

from elasticsearch-operator.

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

from elasticsearch-operator.

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

from elasticsearch-operator.

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

from elasticsearch-operator.

@openshift-bot: Closing this issue.

from elasticsearch-operator.