After a recent update to our flyte helm chart, rec...
# ask-the-communityl
Louis DiNatale
12/15/2022, 4:34 PMAfter a recent update to our flyte helm chart, recovery has stopped working. We can relaunch still but we are getting an error
Copy code
Failed to check the existence of deck file.Louis DiNatale
12/15/2022, 4:34 PMWe get that error in the propellor when we hit recover
l
Louis DiNatale
12/15/2022, 4:40 PMperfect thanks dan
y
Yee
12/15/2022, 9:02 PM
https://github.com/flyteorg/flyteplugins/blob/902b902fcf487f30ebb5dbeee3bb14e17eb0ec21/go/tasks/pluginmachinery/flytek8s/config/config.go#L133 @Matt Coan this is the config option in case you haven’t found it already
Yee
12/15/2022, 9:03 PM
let’s bump that to 8 mins. should be enough.
l
Louis DiNatale
12/15/2022, 9:03 PMPerfect thank you so much
y
Yee
12/15/2022, 9:03 PM
Copy code
// This may consist of:
// 1. Transient errors: e.g. failed to reserve
// container name, container name [...] already in use
// by container
// 2. Permanent errors: e.g. no command specified
// To handle both types of errors gracefully without
// arbitrary pattern matching in the message, we simply
// allow a grace period for kubelet to resolve
// transient issues with the container runtime.Yee
12/15/2022, 9:04 PM
to “handle both types of errors gracefully…”
152 Views