You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Trying to deploy a service containing a Helm hook will still apparently hang the CLI because of how Helm hooks work: https://helm.sh/docs/topics/charts_hooks/
There is a feature request on Helm on how they will address this, but still under development: helm/helm#10555
We can think about doing the installation in background (goroutine?) without the client waiting.
deploy the service on epinio v1.8.1 to reproduce the issue:
epinio service create simplejob smp2
🚢 Creating Service...
Catalog: simplejob
Service: smp2
Wait For Completion: false
❌ error creating service: service create failed: Internal Server Error: error deploying service helm chart: failed post-install: timed out waiting for the condition
update to latest epinio-server by make patch-epinio-deployment
deploy the service on updated epinio
./dist/epinio-linux-amd64 service create simplejob smp4
🚢 Creating Service...
Catalog: simplejob
Service: smp4
Wait For Completion: false
The service creation command doesn't hang anymore and returns immediately, but anyway the service won't be deployed because the job is waiting for 9999d to finish.
Ref: #2136
Describe the bug
Trying to deploy a service containing a Helm hook will still apparently hang the CLI because of how Helm hooks work: https://helm.sh/docs/topics/charts_hooks/
There is a feature request on Helm on how they will address this, but still under development: helm/helm#10555
We can think about doing the installation in background (goroutine?) without the client waiting.
To Reproduce
Try to deploy a service with an hanging Job/hook: https://github.com/enrichman/helm-charts/tree/main/charts/simplejob
Installing this service will wait for the Job completion.
Expected behavior
Without the
--wait
flag I'm expecting the CLI to exit immediately without waiting for the service deployment.The text was updated successfully, but these errors were encountered: