PipelineRun takes a lot of time to get started on OpenShift Container Platform 4

Solution Verified - Updated -

Issue

  • We sometimes observe that a created PipelineRun doesn't start immediately. The PipelineRun is created and visible in the WebUI but the associated pods do not start and it can take up to 7 minutes until it eventually starts.
  • Tekton PipelineRun doesn't always start immediately.

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4
  • Red Hat OpenShift Pipelines 1

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