+++ This bug was initially created as a clone of Bug #1824298 +++ +++ This bug was initially created as a clone of Bug #1824285 +++ Description of problem: crio panic is occurring on all release branches during e2e tests. 4.5 is using cri-o.x86_64 0:1.17.3-1 (still using 1.17 crio as there is not a 1.18 package yet) 4.4 is using cri-o.x86_64 0:1.17.3-1 4.3 is using cri-o.x86_64 0:1.16.5-1 Apr 15 13:17:05.708827 ip-10-0-138-245.ec2.internal crio[1376]: panic: attempted to update last-writer in lockfile without the write lock Apr 15 13:17:05.709217 ip-10-0-138-245.ec2.internal crio[1376]: goroutine 27322 [running]: Apr 15 13:17:05.709558 ip-10-0-138-245.ec2.internal crio[1376]: panic(0x558f9fe35ca0, 0x558fa0179370) Version-Release number of selected component (if applicable): cri-o.x86_64 0:1.17.3-1 cri-o.x86_64 0:1.16.5-1 How reproducible: Happens continuously in CI. Example: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_installer/3276/pull-ci-openshift-installer-master-e2e-aws-scaleup-rhel7/5649 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
PR attached
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-2020:2184