You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2023/01/17 19:42:24 UTC
[GitHub] [superset] caparisi opened a new issue, #22757: Helm: Job init-db doesn't support concurent release in same namespace
caparisi opened a new issue, #22757:
URL: https://github.com/apache/superset/issues/22757
We deploy many Superset by Helm chart in the same Kubernetes Cluster (and same namespace). Each helm release have a unique name, but all release will create the job to init the db with the name `superset-init-db`, which create conflict ( fail with `Hook post-install superset/templates/init-job.yaml failed: jobs.batch "superset-init-db" already exists`, DB not initialized ....)
#### How to reproduce the bug
1. Deploy many (3-4) Helm char in same time
2. Look your pods, you will see some job be interrupt to be replace by a other one from a other release
3. Look your jobs, you will see only 1 job `superset-init-db` whatever the number of release run in same time
### Expected results
We expect 1 job `superset-init-db` by Helm release
### Actual results
We have only 1 job for all Helm release which include the specific release name `my-custom-superset-name-init-db`
### Environment
- HELM chart version: 0.7.6
- superset version: 1.5.3
### Additional context
The root cause look like to come from the job template (https://github.com/apache/superset/blob/master/helm/superset/templates/init-job.yaml#L21) which use `superset.name` instead of `superset.fullname` like in deployment template.
--
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: Job init-db doesn't support concurrent release in same namespace [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #22757:
URL: https://github.com/apache/superset/issues/22757#issuecomment-1958310052
Closing this as stale since it's been silent for so long, and we're trying to steer toward a more actionable Issues backlog. If people are still encountering this in current versions (currently 3.x) please re-open this issue, open a new Issue with updated context, or raise a PR to address the problem. Thanks!
--
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: Job init-db doesn't support concurrent release in same namespace [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #22757: Helm: Job init-db doesn't support concurrent release in same namespace
URL: https://github.com/apache/superset/issues/22757
--
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: Job init-db doesn't support concurrent release in same namespace [superset]
Posted by "caparisi (via GitHub)" <gi...@apache.org>.
caparisi commented on issue #22757:
URL: https://github.com/apache/superset/issues/22757#issuecomment-1959107868
We still have the issue, please keep it alive :smile_cat:
--
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: Job init-db doesn't support concurrent release in same namespace [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #22757:
URL: https://github.com/apache/superset/issues/22757#issuecomment-1960283453
Re-opening, but can you add some context, or what might have changed lately, if anything? If nobody else has complained in over a year, there must be a workaround or something... I'm not sure what to make of 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: Job init-db doesn't support concurrent release in same namespace [superset]
Posted by "craig-rueda (via GitHub)" <gi...@apache.org>.
craig-rueda commented on issue #22757:
URL: https://github.com/apache/superset/issues/22757#issuecomment-1960302332
This type of use case is fairly non-standard. Typically, an instance of superset should be installed in its own namespace.
--
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