CronJob in OpenShift Container Platform 4 is failing but was previously working on OpenShift Container Platform 3

Solution Verified - Updated -

Issue

  • One of our applications uses CronJob to trigger activity on scheduled basis. It works perfectly fine on OCP 3.11 but fails on 4.6 with very strange events as shown below.

    3m23s       Warning   FailedCreatePodSandBox   pod/job-XXXXXXXX-YYYYY   (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = container create failed: time="2021-03-12T14:05:57Z" level=error msg="container_linux.go:366: starting container process caused: process_linux.go:472: container init caused: read init-p: connection reset by peer"
    

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