Hide Forgot
Description of problem: Saw many tests to fail, investigated further and found out the node is tainted with a "PLEG is not healthy: pleg was last seen active 19m28.423484988s ago; threshold is 3m0s." condition https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.2/2435 https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.2/2435/artifacts/e2e-aws/nodes.json Additional info: Not sure if this is related to the existing https://bugzilla.redhat.com/show_bug.cgi?id=1636053 and/or https://bugzilla.redhat.com/show_bug.cgi?id=1613808, both are reported for 3.x, while this is 4.2 development.
Container runtime going down is high or above severity.
(partial) mitigation https://github.com/cri-o/cri-o/pull/2655 potential fix https://github.com/containers/storage/pull/399 upstream cri-o issue mirroring this bz https://github.com/cri-o/cri-o/issues/2584
No occurrences in CI in the last 14 days. Seems to be fixed. https://search.svc.ci.openshift.org/?search=pleg+was+last+seen+active&maxAge=336h&context=2&type=all
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, 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/RHBA-2019:2922