Bug 2056233 - Pods are stuck in a container-creating state in OpenShift 4.8 with kuryr-cni
Summary: Pods are stuck in a container-creating state in OpenShift 4.8 with kuryr-cni
Status: CLOSED DUPLICATE of bug 2028307
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Michał Dulko
QA Contact: Jon Uriarte
Depends On:
TreeView+ depends on / blocked
Reported: 2022-02-20 09:09 UTC by Divyam Pateriya
Modified: 2022-03-01 11:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-02-23 10:59:45 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Divyam Pateriya 2022-02-20 09:09:33 UTC
Description of problem:

Pods are stuck in a container-creating state due to kuryr-cni not being able to assign IP to the Pod.

Version-Release number of selected component (if applicable):

How reproducible:

Happens quite frequently on a specific namespace where more than 300 pods are running.

Steps to Reproduce:

1. Install OpenShift 4.8 on OpenStack with Kuryr.

2. Create a project and deploy 300+ pods within the namespace.

3. Try to rollout deployment/restart the app pods.

Actual results:

kuryr-cni pod is restarting and some pods within the namespace are stuck in ContainerCreating. 

Expected results:

Pods should run just fine.

Additional info:

Crio Logs: https://drive.google.com/file/d/1olEb5B2N6MO-9syIaFnrMuaktHYfrA61/view?usp=sharing

Comment 7 Michał Dulko 2022-02-23 10:59:45 UTC
I'm marking this as a duplicate as there's a fix in 4.8.26 that greatly improves such situations. Please reopen if this proves to include different issues.

*** This bug has been marked as a duplicate of bug 2028307 ***

Note You need to log in before you can comment on or make changes to this bug.