Closed felipejfc closed 8 years ago
Odd, the general issue with timeouts mounting volumes that we were aware was fixed in an earlier k8s version...1.3.4 I think.
Deleting the POD and letting the RC create another one solved the problem.
This seems like a transient k8s error that hasn't been reproduced in our testing. I'm going to close this, but please re-open it if this recurs and there is something Deis Workflow can fix.
This is the pod state:
It was working ok then it suddenly entered this state, looping with this error what is making it unavailable.
Deleting the POD and letting the RC create another one solved the problem.
Deis Workflow version 2.4.1 Kubernetes version 1.3.5 @ AWS