dgrove-oss commented on issue #577: Kafka, Controller and Invoker pods stuck in Init phase, CouchDB not initialized properly URL: https://github.com/apache/openwhisk-deploy-kube/issues/577#issuecomment-578178355 Looks to me like you have most likely some kind of networking problem. The kafka pod's init_container doesn't think zookeeper is ready. ```` Init Containers: wait-for-zookeeper: Container ID: docker://4b9db4e302ddf91200721d537b150c4b28b5942c4a4a71ea9adfe5eba2162881 Image: busybox Image ID: docker-pullable://busybox@sha256:6915be4043561d64e0ab0f8f098dc2ac48e077fe23f488ac24b665166898115a Port: <none> Host Port: <none> Command: sh -c result=1; until [ $result -eq 0 ]; do OK=$(echo ruok | nc -w 1 owdev-zookeeper-0.owdev-zookeeper.openwhisk.svc.kubernetes.default.svc.cluster.local 2181); if [ "$OK" == "imok" ]; then result=0; echo "zookeeper returned imok!"; else echo waiting for zookeeper to be ready; sleep 1; fi; done; echo "Success: zookeeper is up" State: Running Started: Fri, 24 Jan 2020 10:59:56 +0000 Ready: False Restart Count: 0 Environment: <none> Mounts: /var/run/secrets/kubernetes.io/serviceaccount from default-token-bjt6q (ro) ``` Either zookeeper really isn't ready (in which case debug why zookeeper isn't starting correctly) or the probe in the can't reach zookeeper to get the expected `imok` response (so debug why the network connectivity isn't as expected).
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
