From 90ac36c1a117818f8168a741dcf9930306269b03 Mon Sep 17 00:00:00 2001
From: Jon Edvald <edvald@gmail.com>
Date: Wed, 27 Feb 2019 14:50:14 +0100
Subject: [PATCH] fix(k8s): don't abort deployment on FailedMount warning

---
 garden-service/src/plugins/kubernetes/status.ts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/garden-service/src/plugins/kubernetes/status.ts b/garden-service/src/plugins/kubernetes/status.ts
index 9e5ffbf5e3..c520948f7b 100644
--- 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") {