KOTS Troubleshooting: Error mounting Volume attachments

Riya Ray
Riya Ray
  • Updated

Author: Riya Ray

Date: February 29, 2024

Audience: Everyone, Self-hosted KOTS

Environmental details: Self-hosted Jama Connect KOTS


The application is not coming up and getting the following error on the logs:

Warning  FailedAttachVolume      19m (x2 over 19m)    attachdetach-controller  AttachVolume. 
Attach failed for volume "pvc-c0fbfe02-97eb-4779-bc3c-92cbb78ffe8d" : rpc error: code = Internal desc = Bad response statusCode [500].
Status [500 Internal Server Error]. Body: [detail=, message=unable to attach volume pvc-c0fbfe02-97eb-4779-bc3c-92cbb78ffe8d to jama: cannot attach volume pvc-c0fbfe02-97eb-4779-bc3c-92cbb78ffe8d because the engine image longhornio/longhorn-engine:v1.2.4 is not deployed on at least one of the the replicas' nodes or the node that the volume is going to attach to, code=Server Error] from [http://longhorn-backend:9500/v1/volumes/pvc-c0fbfe02-97eb-4779-bc3c-92cbb78ffe8d?action=attach]

To resolve this issue, we can scale the core-0 pod down and up. This will initiate a controlled restart/ reset of the affected components, allowing Kubernetes to attempt volume attachments in a cleaner state. 


Workaround 1:

  • On the App server, run the following command:
  • kubectl scale statefulset core-0 --replicas=0
  • Wait for a short amount of time for the scale down to complete. Then run, 
  • kubectl scale statefulset core-0 --replicas=1

Workaround 2:

  • Delete the pod:
  • kubectl delete pods [podName]
  • Delete the statefulset of the pod:
  • kubectl delete statefulsets [podName]

Additional Information/Metadata:

  • Troubleshooting
  • Jama Connect KOTS

Feedback: Please leave feedback in the comments below.


Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request



Please sign in to leave a comment.