title: Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[dshm data]: timed out waiting for the condition
body: <p>I have a Kubernetes cluster crashing consistently due to the following error</p>
  <pre><code>Pod keycloak-postgresql-0
  Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[dshm data]: timed out waiting for the condition 
  </code></pre>
  <p>which almost certainly leads later to this error</p>
  <pre><code>Pod keycloak-postgresql-0
  AttachVolume.Attach failed for volume &quot;pvc-94b61d69-b529-4b0b-bef3-4b85880a0e71&quot; : instance not found 
  </code></pre>
  <p>Although this instance not found error is perplexing as Rancher clearly shows that exact hash <code>pvc-94b61d69-b529-4b0b-bef3-4b85880a0e71 </code> under the &quot;bound&quot; state of PersistentVolumes. While I'm fairly new to k8s, this seems like the wrong error</p>
  <p>Based on the similar nature to the error, I thought <a href="https://stackoverflow.com/questions/69544012/unable-to-attach-or-mount-volumes-timed-out-waiting-for-the-condition">this fix</a> would be relevant and tried creating an extra PVC to overcome the limitation but the errors persisted</p>
  <p>At one point it was working before redeploying so the error is isolated to a cluster config issue but I have no way of figuring out comparing the previous setup to the current one</p>
  <p>The keycloak-postgresql pod also never becomes &quot;ready&quot; but doesn't produce any logs even when redeployed if that info helps in any way</p>