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
test: Move the prometheus alerts test to the beginning of the suite #24499
test: Move the prometheus alerts test to the beginning of the suite #24499
Conversation
Otherwise some tests trigger temporary alerts
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: smarterclayton 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 |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
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.
Hmm what is a temporary alert? If it’s valid to be temporary we should just include it in the list of excluded alerts we check against.
I think alert check should be at the end and do a rate, I already am working on that. Because we want to make sure no alerts are firing throughout the duration of the cluster being up. This is because some might be in pending state and this won’t catch them.
/hold Testing for firing alerts shouldn't be done at the beginning of the test suite. Doing this can lead to shipping OpenShift installation with firing alerts.
Second solution would need tweaking test expression to allow |
Note that I already started working on end of run tests for alerts checking. #24492 it detects correctly the OLM alert that is firing every time, whereas we have been seeing flakes which is why I suspect this PR was opened. ( Note that the PR is in WIP. Feedback welcome. :) |
Excluding |
Going to merge this now while we sort out how to suppress temporary alerts during runs in serial, disruptive, and upgrade tests (which will always generate some number of fired alerts). |
/retest Please review the full test history for this PR and help us cut down flakes. |
8 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
Otherwise some tests trigger temporary alerts