fix(k8s): don't abort deployment on FailedMount warning

garden-io · Feb 27, 2019 · 90ac36c · 90ac36c
1 parent f14cde8
commit 90ac36c
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/garden-service/src/plugins/kubernetes/status.ts b/garden-service/src/plugins/kubernetes/status.ts
@@ -173,10 +173,10 @@ export async function checkDeploymentStatus(
     }
 
     if (event.type === "Warning" || event.type === "Error") {
-      if (event.type === "Warning" && event.reason === "FailedScheduling") {
+      if (event.type === "Warning" && (event.reason === "FailedScheduling" || event.reason === "FailedMount")) {
         // this can happen on first attempt to schedule a pod
         // TODO: we may want to more specifically look at the message
-        //       (e.g. 'pod has unbound immediate PersistentVolumeClaims')
+        //       (e.g. 'pod has unbound immediate PersistentVolumeClaims' or 'couldn't propagate object cache')
         continue
       }
       if (event.reason === "Unhealthy") {