Pod is not restarted after a node reboot in a HCP OpenShift cluster

Solution Verified - Updated -

Issue

  • In a HCP OpenShift cluster running on OpenShift Virtualization platform, a bare metal node has been restarted. An application running in a pod of the hosted cluster is not recovered because the affected pod is not restarted.
  • Pod uses a Filesystem PVC from a storage class provided by the CSI KuberVirt driver.
  • Pod is stuck in deletion indefinitely.

Environment

  • OpenShift Container Platform (OCP) 4.18.9
  • OpenShift Virtualization 4.18.8
  • Hosted Control Planes (HCP)
  • Multicluster engine for Kubernetes (MCE) 2.8.3
  • Advanced Cluster Management for Kubernetes (ACM) 2.13.3

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