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 2022/04/07 14:37:29 UTC

[GitHub] [superset] riazarbi commented on issue #19588: Helm upgrade from 0.5.8 to 0.5.9 fails

riazarbi commented on issue #19588:
URL: https://github.com/apache/superset/issues/19588#issuecomment-1091817366

   Alright, I fixed my own problem in an unsatisfactory kind of way. 
   
   It appears the root cause is that the redis image tag was bumped. Statefulsets don't allow you to do this, so the upgrade fails. 
   
   I managed to get past it by setting 
   
   ```
   redis:
     enabled: false
   ```
   
   In order to upgrade from 0.5.8 to 0.5.9. 
   
   Since the statefulset was no longer part of the spec, the upgrade succeeded. But of course superset was broken because I don't have a separate redis endpoint. 
   
   _Then_ I changed the values.yaml back to
   
   ```
   redis:
     enabled: true
   ```
   
   
   And updated the values in the redis section as per this commit - https://github.com/apache/superset/commit/33d1c967649890500fb788678e8a10afc08bc99a
   
   And then redeployed for 0.5.9 _again_ s that this time the redis statefulset _is_ part f the deployment and hey presto, it's working. 
   
   Bear in mind this solution will result in some downtime if you try 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