Bug 1601370

Summary: Failed to create pod with FailedCreatePodSandBox error
Product: Container Native Virtualization (CNV) Reporter: Vatsal Parekh <vparekh>
Component: InstallationAssignee: Steve Reichard <sreichar>
Status: CLOSED NOTABUG QA Contact: Lukas Bednar <lbednar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.1CC: fsimonce, ncredi, rhallise, vparekh
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-20 09:36:55 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:

Description Vatsal Parekh 2018-07-16 08:25:09 UTC 
Description of problem:
I am seeing CDI pod stuck in ContainerCreating from a day, with the following in the events

LAST SEEN   FIRST SEEN   COUNT     NAME                                              KIND      SUBOBJECT   TYPE      REASON                   SOURCE                                             MESSAGE
4m          1d           9483      cdi-deployment-56976686f-ph5tq.1541576e1055c89a   Pod                   Warning   FailedCreatePodSandBox   kubelet, cnv-executor-vatsal-master1.example.com   Failed create pod sandbox: rpc error: code = Unknown desc = pod sandbox with name "k8s_cdi-deployment-56976686f-ph5tq_golden-images_983a8574-87a6-11e8-b862-fa163edc19ee_0" already exists

Though, it started working after I deleted the pods, and it got scheduled again successfully 

Version-Release number of selected component (if applicable):
0.7alpha5, CDI 0.5

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Ryan Hallisey 2018-07-16 12:30:26 UTC 
Was this a fresh environment? I'm wondering if there was a pod lying around from an old deploy that conflicted.  Can you re test?
Comment 2 Vatsal Parekh 2018-07-16 12:41:13 UTC 
(In reply to Ryan Hallisey from comment #1)
> Was this a fresh environment? I'm wondering if there was a pod lying around
> from an old deploy that conflicted.  Can you re test?

Yes it was a fresh env, but when I deleted that pod and deployment recreated it, worked now
Comment 3 Steve Reichard 2018-07-16 20:13:45 UTC 
This looks like it is upstream, the BZs are for the downstream CNV.
Comment 4 Steve Reichard 2018-07-17 12:31:58 UTC 
Vatsal,

If this is working for you now, can it be closed?
Comment 5 Vatsal Parekh 2018-07-20 09:36:55 UTC 
Yes, can be closed now