-
Notifications
You must be signed in to change notification settings - Fork 370
test/e2e: Make sure Prometheus only fires Watchdog alert #266
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
Conversation
This needs a rebase, otherwise lgtm. |
9883d68
to
f00462d
Compare
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mxinden, s-urbaniak The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
whoops, I missed that we are still firing |
No worries @s-urbaniak, I added the |
Kicking off a retest as #275 is merged. /retest |
- Rename `pkg/client.DeleteIfExists` to `DeleteNamespaceIfExists`. - Fix `pkg/clinet.DeleteNamespaceIfExists` error message on failure.
f00462d
to
4662fb5
Compare
New changes are detected. LGTM label has been removed. |
I think we were talking about that this should rather be part of the |
Yes, that sounds good @brancz. On a current Openshift 4.0 cluster TargetDown alert is firing for job="catalog-operator-metrics", job="sdn" and job="olm-operator-metrics". |
This one might be a bit trickier, but I will move it into |
I don't think we've ever added a test to that suite, keep us updated :) |
In my local cluster Prometheus fires the
KubeClientCertificateExpiration
alert. Once we resolved that we can continue here. Opening it up for early feedback.