Document Common CI/CD Timeout Error

[osterman]

what

"chart-repo" has been added to your repositories                                                                                
exec: helm repo update --kube-context us-west-2-staging-example-co                                                                
Hang tight while we grab the latest from your chart repositories...                                                             
...Successfully got an update from the "cloudposse-incubator" chart repository                                                  
...Successfully got an update from the "stable" chart repository                                                                
...Successfully got an update from the "chart-repo" chart repository                                                            
Update Complete. ⎈ Happy Helming!⎈                                                                                              
exec: helm upgrade --install ch38827-app chart-repo/app --version 1.0.0-sha.1dd6919 --namespace ch38827 --values /code
fresh/volume/app/config/ch38827-app.yaml --wait --timeout=600 --recreate-pods --force --reset-values --kube
-context us-west-2-staging-example-co                                                                                             
Error: UPGRADE FAILED: timed out waiting for the condition                                                                      
err: exit status 1                                                                                                              
[SYSTEM] Error: Failed to run freestyle step: Deploy app with helmfile; caused by NonZeroExitCodeError: Container for step 
title: Deploy app with helmfile, step type: freestyle, operation: Freestyle step failed with exit code: 1                  

why

• in my experience, that always happens when a pod is failing
• basically helm --wait will wait until a successful rollout
• since the pod is failing, it's never successful, so it ends up failing after the timeout window (edited)
• start by inspecting the pods status / logs to see what's going on

[kuinak]

FWIW, kubectl describe pod was instrumental in determining why my pod wasn't starting up

[osterman]

thanks!

[osterman]

incidentally, this just helped someone else out =)