Pods in "openshift-cluster-csi-drivers" stay "Pending" during upgrade to OpenShift Container Platform 4.6

Solution Verified - Updated -

Issue

  • During the Upgrade from OpenShift Container Platform 4.5 to OpenShift Container Platform 4.6, Pods in the openshift-cluster-csi-drivers stay in the Pending status.
  • Scheduling of aws-ebs-csi-driver-node-* Pods fails with the following error messsages:

    - 0/10 nodes are available: 1 node(s) didn't match node selector, 9 node(s) didn't have free ports for the requested pod ports.
    - pod didn't trigger scale-up (it wouldn't fit if a new node is added): 2 node(s) didn't match node selector, 1 max node group size reached
    
  • The Cluster Storage Operator stays in the "Progressing" state and is stuck with the following error message:

    AWSEBSCSIDriverOperatorCRProgressing: AWSEBSDriverNodeServiceControllerProgressing: Waiting for DaemonSet to deploy node pods
    

Environment

  • Red Hat OpenShift Container Platform (OCP) 4.6
  • Amazon Web Services (AWS)

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