You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installing Zookeeper using Helm fails. Post install upgrade hook job fails because ZookeeperCluster information is incorrect. The installation is being performed on a MacBookPro with 64GB RAM using Minikube.
It appears the ZookeeperCluster information for the zookeeper PODs is not updated properly causing key checks to fail in the post-install-upgrade-hook script.
Check the status of the PODs - it is not ready as you can see below. In addition, status.currentVersion is NOT set.
> kubectl get ZookeeperCluster -n default zookeeper -o json
> kubectl get all
NAME READY STATUS RESTARTS AGE
pod/client-tools-8448f964c4-sxw5c 1/1 Running 0 19h
pod/zookeeper-0 1/1 Running 0 30s
pod/zookeeper-operator-f579bfcf5-srpl8 1/1 Running 0 68m
pod/zookeeper-post-install-upgrade--1-f6qcm 1/1 Running 0 29s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 2d22h
service/zookeeper-admin-server ClusterIP 10.100.65.88 <none> 8080/TCP 30s
service/zookeeper-client ClusterIP 10.106.174.190 <none> 2181/TCP 30s
service/zookeeper-headless ClusterIP None <none> 2181/TCP,2888/TCP,3888/TCP,7000/TCP,8080/TCP 30s
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/client-tools 1/1 1 1 19h
deployment.apps/zookeeper-operator 1/1 1 1 68m
NAME DESIRED CURRENT READY AGE
replicaset.apps/client-tools-8448f964c4 1 1 1 19h
replicaset.apps/zookeeper-operator-f579bfcf5 1 1 1 68m
NAME READY AGE
statefulset.apps/zookeeper 1/1 30s
NAME COMPLETIONS DURATION AGE
job.batch/zookeeper-post-install-upgrade 0/1 29s 29s
Check ZookeepCluster information again and you see the below - which does not make sense. readyReplicas is 1 but members listed under unready section. Also, we can see status.currentVersion is not set. Overall, many checks fail in post-install-uprgade-hook script causing the installation to fail.
Description
Installing Zookeeper using Helm fails. Post install upgrade hook job fails because ZookeeperCluster information is incorrect. The installation is being performed on a MacBookPro with 64GB RAM using Minikube.
Importance
Blocker
Location
https://github.com/pravega/zookeeper-operator/blob/master/charts/zookeeper/templates/post-install-upgrade-hooks.yaml#L66
Suggestions for an improvement
It appears the ZookeeperCluster information for the zookeeper PODs is not updated properly causing key checks to fail in the post-install-upgrade-hook script.
> kubectl get ZookeeperCluster -n default zookeeper -o json
> kubectl get ZookeeperCluster -n default zookeeper -o json
The text was updated successfully, but these errors were encountered: