youngwookim commented on issue #156:
URL: 
https://github.com/apache/apisix-helm-chart/issues/156#issuecomment-942305368


   @tokers 
   
   Rollback to 0.4.0 chart:
   ```
   $ helm list -n apisix
   NAME         NAMESPACE       REVISION        UPDATED                         
        STATUS          CHART           APP VERSION
   apisix       apisix          2               2021-10-12 12:26:19.228653 
+0900 KST    deployed        apisix-0.6.0    2.10.0     
   [ywkim: ~]$ helm rollback -n apisix apisix
   Rollback was a success! Happy Helming!
   [ywkim: ~]$ helm list -n apisix
   NAME         NAMESPACE       REVISION        UPDATED                         
        STATUS          CHART           APP VERSION
   apisix       apisix          3               2021-10-13 22:18:23.102311 
+0900 KST    deployed        apisix-0.4.0    2.7.0      
   ```
   
   No difference, I got same message from pod:
   ```
   etcd 13:23:13.58 
   etcd 13:23:13.58 Welcome to the Bitnami etcd container
   etcd 13:23:13.58 Subscribe to project updates by watching 
https://github.com/bitnami/bitnami-docker-etcd
   etcd 13:23:13.58 Submit issues and feature requests at 
https://github.com/bitnami/bitnami-docker-etcd/issues
   etcd 13:23:13.58 
   etcd 13:23:13.58 INFO  ==> ** Starting etcd setup **
   etcd 13:23:13.59 INFO  ==> Validating settings in ETCD_* env vars..
   etcd 13:23:13.60 WARN  ==> You set the environment variable 
ALLOW_NONE_AUTHENTICATION=yes. For safety reasons, do not use this flag in a 
production environment.
   etcd 13:23:13.60 INFO  ==> Initializing etcd
   etcd 13:23:13.60 INFO  ==> Detected data from previous deployments
   etcd 13:23:23.86 INFO  ==> Updating member in existing cluster
   Error: bad member ID arg (strconv.ParseUint: parsing "": invalid syntax), 
expecting ID in Hex
   ```


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to