Bug 1850168

Summary: [CRI-O] CRI-O reports container as exited although the process is still running
Product: OpenShift Container Platform Reporter: Dan Kenigsberg <danken>
Component: NodeAssignee: Peter Hunt <pehunt>
Status: CLOSED ERRATA QA Contact: Sunil Choudhary <schoudha>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, cpaquin, danken, dvossel, dwalsh, fdeutsch, jokerman, minmli, mpatel, nagrawal, ncredi, pehunt, pelauter, rgarcia, rmohr, roman, tsweeney, vromanso, xtian, yadu, ycui, zyu
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: runc-1.0.0-69.rhaos4.4.git81f3917.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1843470 Environment:
Last Closed: 2020-07-06 20:47:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1843470    
Bug Blocks: 1837182    

Comment 3 Yan Du 2020-07-01 13:24:30 UTC
Test on Build 44.81.202006271430-0
runc-1.0.0-69.rhaos4.4.git81f3917.el8.x86_64

Issue can not be reproduced.

$ oc get vmi
NAME   AGE   PHASE     IP            NODENAME
vma    29h   Running   10.0.2.2/24   yadu-ocp44new-d6rqb-worker-l8gkz
vmb    29h   Running   10.0.2.2/24   yadu-ocp44new-d6rqb-worker-l8gkz

$ oc get pod
NAME                      READY   STATUS    RESTARTS   AGE
virt-launcher-vma-npr9q   2/2     Running   0          29h
virt-launcher-vmb-7c2cv   2/2     Running   0          29h

Comment 5 errata-xmlrpc 2020-07-06 20:47:17 UTC
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:2786