-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failed to create or get service for metrics #205
Comments
Hi, i get it too, there is a way that i can handle this problem for now? |
How did you deploy the 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. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Starting the ElasticSearch operator on OpenShift, we would find the following warning:
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 anownerReference
to my operator deployment.Source image for the ElasticSearch operator pod: registry.redhat.io/openshift4/ose-elasticsearch-operator@sha256:69968bc98d29773b89ba9b3c3c5b1fc44d8df5226934683e3029ae14f4829fab
The text was updated successfully, but these errors were encountered: