Bug 1505354

Summary: OpenShift unable to delete pods which failed ContainerCreating using cri-o (missing CreatedAt field)
Product: OpenShift Container Platform Reporter: Sebastian Jug <sejug>
Component: ContainersAssignee: Mrunal Patel <mpatel>
Status: CLOSED ERRATA QA Contact: weiwei jiang <wjiang>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.7.0CC: aos-bugs, jeder, jhonce, jokerman, mmccomas, xtian
Target Milestone: ---Keywords: NeedsTestCase
Target Release: 3.7.0   
Hardware: All   
OS: Linux   
Whiteboard: aos-scalability-37
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-28 22:18:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
CRIO Journal log none

Comment 1 Seth Jennings 2017-10-23 15:10:11 UTC 
crio is running on this node and is having issues.  There are stack traces in the journal.  I extracted the last 24hrs of journal from the node for debugging:

http://file.rdu.redhat.com/sjenning/bz1505354-node.log

Routing to Containers for further investigation.
Comment 2 Sebastian Jug 2017-10-23 18:31:52 UTC 
Created attachment 1342360 [details]
CRIO Journal log
Comment 3 Mrunal Patel 2017-10-23 20:26:29 UTC 
I have opened https://github.com/kubernetes-incubator/cri-o/pull/1053 which should be tested to see if it fixes the godbus panic.
Comment 4 Sebastian Jug 2017-10-24 19:23:37 UTC 
The updated godbus library does seem to fix the panic.
Comment 5 Mrunal Patel 2017-10-26 17:04:57 UTC 
This is fixed in cri-o 1.0.1
Comment 7 weiwei jiang 2017-11-03 09:11:28 UTC 
Checked with:
# openshift version 
openshift v3.7.0-0.188.0
kubernetes v1.7.6+a08f5eeb62
etcd 3.2.8

crio version 1.0.2
commit: "29077fa6fbd85f0ca9c453ab1bf1ff7b02bc3f5c"

And can not reproduce this issue. So verify this.
Comment 10 errata-xmlrpc 2017-11-28 22:18:47 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/RHSA-2017:3188