Cluster upgrade stuck with AWSEBSCSIDriverOperatorCRDegraded due to `volumesnapshotclass.yaml` timeout

Solution Verified - Updated -

Issue

  • Cluster with low API performance
  • Encountering a blocking issue during the OpenShift cluster upgrade where the ClusterOperator Storage is degraded. The following message is repeatedly observed in the status conditions:
- lastTransitionTime: "2025-06-07T08:53:57Z"
  message: "AWSEBSCSIDriverOperatorCRDegraded: AWSEBSDriverConditionalStaticResourcesControllerDegraded:
    \"volumesnapshotclass.yaml\" (string): the server was unable to return a response
    in the time allotted, but may still be processing the request\nAWSEBSCSIDriverOperatorCRDegraded:
    AWSEBSDriverConditionalStaticResourcesControllerDegraded:"
  reason: AWSEBSCSIDriverOperatorCR_AWSEBSDriverConditionalStaticResourcesController_S
  • Confirmed that the VolumeSnapshotClass resource either exists or is being created eventually, yet the operator remains in a degraded state.

  • The operator still degraded after stabilizing API

Environment

  • OpenShift Container Platform 4.x
  • Amazon EBS gp3 volume

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