Hide Forgot
Created attachment 1784811 [details] Screenshot showing intermittent downtime in the kubelet metrics endpoints Description of problem: The kubelet metrics endpoints are intermittently unavailable during single-node e2e tests on AWS. See `up = 0` query attached screenshot that shows it quite clearly. This sometimes causes the TargetDown alert (https://github.com/openshift/cluster-monitoring-operator/blob/30339d233720f96dc3ecaf5059bd150aec6735f6/assets/cluster-monitoring-operator/prometheus-rule.yaml#L16-L30) to be raised. Version-Release number of selected component (if applicable): Happened in this nightly https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.8-e2e-aws-single-node/1394805313575587840 How reproducible: Steps to Reproduce: Happens during single node e2e nightlies https://testgrid.k8s.io/redhat-single-node#periodic-ci-openshift-release-master-nightly-4.8-e2e-aws-single-node Actual results: Kubelet metrics endpoints shouldn't have significant downtime Expected results: They have significant intermittent downtime Additional info:
testing pr https://github.com/openshift/kubernetes/pull/755
tested with 4.8.0-0.nightly-2021-05-25-180327, searched with up == 0, did not see kubelet service down within 2 hours
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438