The application pods are stuck in the Init:0/1 state

Solution Verified - Updated -

Issue

The application pods are stuck in the Init:0/1 state during the deployment rollout or during the pod restart with the following error messages in the kubelet logs on the node.

Oct 18 11:41:08 <NodeName> hyperkube[3802345]: E1018 11:41:08.250087 3802345 manager.go:1123] Failed to create existing container: /kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod5b415118_2312_48d9_b625_6af811cf3579.slice/crio-b474b2ef4e1409be548415b7275d7629f4d54699beda7f572d84e752dcd28fb2.scope: Error finding container b474b2ef4e1409be548415b7275d7629f4d54699beda7f572d84e752dcd28fb2: Status 404 returned error &{%!s(*http.body=&{0xc002fe2be0 <nil> <nil> false false {0 0} false false false <nil>}) {%!s(int32=0) %!s(uint32=0)} %!s(bool=false) <nil> %!s(func(error) error=0x790ae0) %!s(func() error=0x790a60)}

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content