You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "kalkrishnan (via GitHub)" <gi...@apache.org> on 2023/06/05 15:30:01 UTC

[GitHub] [superset] kalkrishnan opened a new issue, #24292: Helm install timed out waiting for condition

kalkrishnan opened a new issue, #24292:
URL: https://github.com/apache/superset/issues/24292

   A clear and concise description of what the bug is.
   
   #### How to reproduce the bug
   
   1. Ran the helm command to install superset as provided in documentation:
   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):
   
   - superset version: latest helm chart
   
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
   - [ ] I have reproduced the issue with at least the latest released version of superset.
   - [ ] I have checked the issue tracker for the same issue and I haven't found one similar.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] Helm install timed out waiting for condition [superset]

Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #24292:
URL: https://github.com/apache/superset/issues/24292#issuecomment-1981886057

   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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] matheuscarreirod commented on issue #24292: Helm install timed out waiting for condition

Posted by "matheuscarreirod (via GitHub)" <gi...@apache.org>.
matheuscarreirod commented on issue #24292:
URL: https://github.com/apache/superset/issues/24292#issuecomment-1655742360

   i'm having the same issue, did you solve it?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] Helm install timed out waiting for condition [superset]

Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #24292: Helm install timed out waiting for condition
URL: https://github.com/apache/superset/issues/24292


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org