OLM-managed operator install or update requests may time out on OpenShift 4.8

Solution Verified - Updated -

Issue

In OpenShift 4.8, users maybe be unable to install or upgrade any operators due to slow response times from the default redhat-operators and community-operators CatalogSources. The Catalog Operator that is part of OpenShift's Operator Lifecycle Manager expects CatalogSources to return a response to its gRPC requests within 1 minute. In OpenShift 4.8 the catalogs can take roughly 2 minutes to fulfill requests. Failure to respond within a minute caused the Catalog Operator to "give up" on installing on anything, preventing any operator installations/upgrades.

These issues aren't present on OpenShift 4.9 and newer releases.

This issue may prevent you from updating from an older version than OpenShift 4.8, to OpenShift 4.8 and then subsequently to newer OpenShift releases, if updating operators is required to complete an update to OpenShift 4.8.

Environment

  • OpenShift 4.8
  • default CatalogSource instances of redhat-operators or community-operators with original content set (not mirrored or filtered)
  • optional: updating to OpenShift 4.8 and installed operators as an intermediate step towards updating to newer versions of OpenShift

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