-
Notifications
You must be signed in to change notification settings - Fork 350
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
chore(e2e): add test for Prometheus trait #1547 #1849
Conversation
Hi @tadayosi, the tests fail because the ServiceMonitor CRD is not installed:
It fails also on OpenShift 3.11 for the same reason. The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@astefanutti Thanks for your feedback. I'm not certain what's really happening with the openshift integration test though, as the output log shows that it didn't run on OpenShift according to:
So I have an impression that it's failing just due to #1848. It makes sense to add |
This is the
It fails also on OpenShift workflow, because that is OpenShift 3.11 and the Prometheus operator isn't installed OOTB, as opposed to OCP 4. |
@astefanutti Ah you are right. I was confused on Let me try adding |
Hmm, so it appears that what blocks the test now is #1848. It seems Prometheus trait doesn't deploy not only on k8s but also OCP 3.11. |
Minikube doesn't have the Prometheus operator installed OOTB either, so it fails with the same error. The option to disable the creation of the ServiceMonitor should also be added on vanilla Kubernetes. |
I'm trying to fix #1848 first. |
This can be rebased as #1848 has been merged. |
6be4947
to
42c031a
Compare
It passes fine on OCP but there is a known issue with Minikube #1848.
Release Note