Operator catalog Pods created by CatalogSource do not schedule on other nodes even if the node is down.

Solution In Progress - Updated -

Issue

  • Operator catalog pod created by catalogsource do not get scheduled on other nodes if the node is abruptly shutdown.
  • The pod is also observed as Running state.

Environment

  • Red Hat OpenShift Container Platform
    • 4.5

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