Why AWS Volumes stuck in attaching state

Solution Verified - Updated -

Issue

  • We have an application using a persistent volume (Jenkins to be specific).
    Often after several application redeploys (eg. after new build or deleting a pod), the volume is stuck in Attaching state in AWS. As a result, the application can no longer be deployed anymore, deleting the pod does not help. To fix the issue, I have to force detach the volume in AWS console. The AWS UI reports a problem with volumes on the instance where it occurs and the system is never back to healthy state without manual intervention.

Environment

  • Openshift Enterprise
  • 3.1

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