hyman-zhou commented on issue #659:
URL: 
https://github.com/apache/openwhisk-deploy-kube/issues/659#issuecomment-745837956


   couchdb can't clone openwhisk
   >>>kubectl logs owdev-init-couchdb-5xx4b -n openwhisk
   Cloning into '/openwhisk'...
   error: RPC failed; curl 18 transfer closed with outstanding read data 
remaining
   fatal: The remote end hung up unexpectedly
   fatal: early EOF
   fatal: index-pack failed
   >>> kubectl get pods -n openwhisk
   NAME                                   READY   STATUS      RESTARTS   AGE
   owdev-alarmprovider-5b86cb64ff-g2kqc   0/1     Init:0/1    0          93m
   owdev-apigateway-bccbbcd67-n8c8f       1/1     Running     0          93m
   owdev-controller-0                     0/1     Init:1/2    0          93m
   owdev-couchdb-584676b956-rmgh5         1/1     Running     0          93m
   owdev-gen-certs-6mb4s                  0/1     Completed   0          93m
   owdev-init-couchdb-5xx4b               0/1     Error       0          62m
   owdev-init-couchdb-r7bgp               0/1     Error       0          67m
   owdev-init-couchdb-r8k4p               0/1     Error       0          93m
   owdev-init-couchdb-zqb6j               0/1     Error       0          81m
   owdev-install-packages-chphp           0/1     Init:0/1    0          93m
   owdev-invoker-0                        0/1     Init:0/1    0          93m
   owdev-kafka-0                          1/1     Running     0          93m
   owdev-kafkaprovider-5574d4bf5f-45wwj   0/1     Init:0/1    0          93m
   owdev-nginx-86749d59cb-thrfx           0/1     Init:0/1    0          93m
   owdev-redis-d65649c5b-kxwds            1/1     Running     0          93m
   owdev-wskadmin                         1/1     Running     0          93m
   owdev-zookeeper-0                      1/1     Running     0          93m


----------------------------------------------------------------
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]


Reply via email to