Open eggfoobar opened 3 weeks ago
@eggfoobar: This pull request explicitly references no jira issue.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: eggfoobar Once this PR has been reviewed and has the lgtm label, please assign bertinatto for approval. For more information see the Code Review Process.
The full list of commands accepted by this bot can be found here.
/hold
Hey @sosiouxme, even though the increase is small, it's odd since HA runs seems to have stayed the same. Could not identify any major changes in the monitoring operator but this all started with the new kubelet version. Will quickly look, but feel free to unblock if you're okay with this change.
@eggfoobar: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
ci/prow/e2e-openstack-ovn | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | false | /test e2e-openstack-ovn |
ci/prow/e2e-gcp-csi | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | false | /test e2e-gcp-csi |
ci/prow/e2e-gcp-ovn | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | true | /test e2e-gcp-ovn |
ci/prow/e2e-aws-ovn-kube-apiserver-rollout | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | false | /test e2e-aws-ovn-kube-apiserver-rollout |
ci/prow/e2e-aws-ovn-fips | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | true | /test e2e-aws-ovn-fips |
ci/prow/e2e-metal-ipi-ovn-ipv6 | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | true | /test e2e-metal-ipi-ovn-ipv6 |
ci/prow/e2e-aws-ovn-edge-zones | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | true | /test e2e-aws-ovn-edge-zones |
ci/prow/e2e-aws-ovn-serial | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | true | /test e2e-aws-ovn-serial |
ci/prow/e2e-aws-csi | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | false | /test e2e-aws-csi |
ci/prow/okd-scos-e2e-aws-ovn | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | false | /test okd-scos-e2e-aws-ovn |
ci/prow/e2e-gcp-ovn-upgrade | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | true | /test e2e-gcp-ovn-upgrade |
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | false | /test e2e-metal-ipi-ovn-kube-apiserver-rollout |
ci/prow/e2e-aws-ovn-single-node-serial | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | false | /test e2e-aws-ovn-single-node-serial |
ci/prow/e2e-agnostic-ovn-cmd | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | false | /test e2e-agnostic-ovn-cmd |
ci/prow/e2e-aws-ovn-cgroupsv2 | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | false | /test e2e-aws-ovn-cgroupsv2 |
ci/prow/e2e-metal-ipi-ovn | 861098f16b5f317d7dd3d97254969f9d6f82d926 | link | false | /test e2e-metal-ipi-ovn |
Full PR test history. Your PR dashboard.
What monitoring operator code change led to this versus the known etcd quorum stability problems?
What monitoring operator code change led to this versus the known etcd quorum stability problems?
At this point, I don't think it has anything to do with the monitoring operator, at least I couldn't identify any change that would cause an added watch count. I wasn't aware of a quorum issue, this PR is just a quick ready to go update since I found it odd that only the monitoring operator was failing here.
Increasing watch count for monitoring operator 110% above p95 for SNO 4.19 runs
(P95 * 1.1)/2 =~ 101