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
check if ClusterMachineApproverDown UsingDeprecatedAPIExtensionsV1Beta1 alerts are not firing #24071
check if ClusterMachineApproverDown UsingDeprecatedAPIExtensionsV1Beta1 alerts are not firing #24071
Conversation
/lgtm |
/retest |
@@ -210,7 +210,7 @@ var _ = g.Describe("[Feature:Prometheus][Conformance] Prometheus", func() { | |||
tests := map[string]bool{ | |||
// Checking Watchdog alert state is done in "should have a Watchdog alert in firing state". | |||
// FIXME(paulfantom): ClusterMachineApproverDown and UsingDeprecatedAPIExtensionsV1Beta1 shouldn't be firing! |
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.
this line can be removed
/retest |
bf0e2e6
to
0dcb9b3
Compare
@simonpasquier removed comment. Putting this on hold as /hold |
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.
/lgtm
#24089 merged |
openshift/cluster-kube-apiserver-operator#639 merged |
/hold cancel |
/retest Please review the full test history for this PR and help us cut down flakes. |
gcp-upgrade flaked on gcp |
/hold |
/test e2e-aws-serial |
@tnozicka failure looks legitimate to me. Log message says:
|
sure, it should fail, yet I see 2 run where it was green https://prow.svc.ci.openshift.org/pr-history/?org=openshift&repo=origin&pr=24071 I am working on a fix, tracing down some more offenders |
Confirmed. Looks like we need to rewrite those tests to be running during a whole test suite run ASAP. |
0dcb9b3
to
ffdb38d
Compare
Rebased to resolve merge conflict |
/retest |
@tnozicka what is the status of fixing |
/retest |
/hold cancel |
…precatedAPIExtensionsV1Beta1 alerts are not firing
ffdb38d
to
71a7b15
Compare
Rebased after changes from #24276 |
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.
/lgtm
🤞
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LiliC, paulfantom, s-urbaniak, simonpasquier 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 Please review the full test history for this PR and help us cut down flakes. |
2 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. |
@tnozicka FYI in the latest nightly 4.4 cluster the |
/retest Please review the full test history for this PR and help us cut down flakes. |
Also the |
/hold Until the alert is fixed, so we don't keep retrying. |
looks like people managed to merge new offenders in the meantime |
@tnozicka Yeah, guess this is why we need to enable them ASAP. Have you considered adding an e2e test to origin instead of an alert for this? As this will be firing on user clusters and I assume a lot of confusion will happen as users can't do anything about this from their side. |
/retest |
With the updated k8s where we DO NOT enable |
Follow-up to #24019.
/cc @lilic @simonpasquier @s-urbaniak