-
Notifications
You must be signed in to change notification settings - Fork 13.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helm install timed out waiting for condition #24292
Comments
i'm having the same issue, did you solve it? |
I'm not sure if this is still an issue in current versions of Superset (3.x). If it is, we can re-open this, or feel free to open a new issue with updated context. We're no longer supporting Superset 2.x or prior, and it's been a while since this thread saw any activity, so I'm closing this as stale. |
I'm running into this issue as well @rusackas
|
@rusackas I found the issue, my server is running an ARM processor and is using arm64, the postgres version referenced in the helm chart is ancient and does not support ARM (only x86): https://hub.docker.com/r/bitnami/postgresql/tags?name=14.6.0-debian-11-r13 You can manually change this by changing the tag, but I think the default probably should be updated to an image that does support both architectures? |
@rusackas : I'm trying to setup superset by following the installation page from docs using minikube but get following error: https://superset.apache.org/docs/installation/kubernetes
Ubuntu server with arm64 architecture
I searched but it seems, the postgre arm64 is not available as mentioned by @jrgilman |
A clear and concise description of what the bug is.
How to reproduce the bug
helm upgrade --install --values values.yaml superset superset/superset --debug
Below is my values.yaml:
supersetNode:
replicaCount: 1
supersetWorker:
replicaCount: 1
configOverrides:
secret: |
SECRET_KEY = '+k2Z2vhUxso2oQwOKqndZ08O7m8kRJHcIumqYZvyxHH9IAPtdh8nnnn'
Expected results
Based on documentation should result in worker pods starting where you can portforward and login
Actual results
Gives the below error:
history.go:56: [debug] getting history for release superset
install.go:200: [debug] Original chart version: ""
install.go:217: [debug] CHART PATH: /private/var/kal/Library/Caches/helm/repository/superset-0.10.1.tgz
client.go:134: [debug] creating 16 resource(s)
client.go:478: [debug] Starting delete for "superset-init-db" Job
client.go:482: [debug] Ignoring delete failure for "superset-init-db" batch/v1, Kind=Job: jobs.batch "superset-init-db" not found
client.go:134: [debug] creating 1 resource(s)
client.go:706: [debug] Watching for changes to Job superset-init-db with timeout of 5m0s
client.go:734: [debug] Add/Modify event for superset-init-db: ADDED
client.go:773: [debug] superset-init-db: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:734: [debug] Add/Modify event for superset-init-db: MODIFIED
client.go:773: [debug] superset-init-db: Jobs active: 1, jobs failed: 1, jobs succeeded: 0
client.go:734: [debug] Add/Modify event for superset-init-db: MODIFIED
client.go:773: [debug] superset-init-db: Jobs active: 1, jobs failed: 2, jobs succeeded: 0
Error: failed post-install: 1 error occurred:
* timed out waiting for the condition
helm.go:84: [debug] failed post-install: 1 error occurred:
* timed out waiting for the condition
State of pods after:
superset-6465bdcf9c-g6kdg 0/1 Init:0/1 4 (2m17s ago) 10m
superset-init-db-5t244 0/1 Init:Error 0 10m
superset-init-db-7l5n8 0/1 Init:Error 0 8m54s
superset-init-db-fvqdq 0/1 Init:Error 0 4m16s
superset-init-db-n47r2 0/1 Init:0/1 0 93s
superset-init-db-vmln5 0/1 Init:Error 0 6m41s
superset-postgresql-0 0/1 Pending 0 10m
superset-redis-master-0 1/1 Running 0 10m
superset-worker-6f99f98c48-67jb6 0/1 Init:0/1 4 (2m17s ago) 10m
The worker keeps crashing and wont let me see any logs as to why
Environment
(please complete the following information):
Checklist
Make sure to follow these steps before submitting your issue - thank you!
The text was updated successfully, but these errors were encountered: