You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2019/08/26 07:28:02 UTC

[GitHub] [openwhisk-deploy-kube] vjykrthk opened a new issue #511: openwhisk-install-packages error

vjykrthk opened a new issue #511: openwhisk-install-packages error
URL: https://github.com/apache/openwhisk-deploy-kube/issues/511
 
 
   $ kubectl --namespace openwhisk get po
   openwhisk-alarmprovider-bd75898fc-vg4tw       1/1     Running     0          60m
   openwhisk-apigateway-868688b5db-msk6r         1/1     Running     0          60m
   openwhisk-cloudantprovider-6d88b978d8-s5lvg   1/1     Running     0          60m
   openwhisk-controller-0                        1/1     Running     0          60m
   openwhisk-couchdb-7ddcff79f8-pb4tm            1/1     Running     0          60m
   openwhisk-init-couchdb-jzxpn                  0/1     Completed   0          60m
   openwhisk-install-packages-gkwz4              0/1     Error       0          60m
   openwhisk-install-packages-kczns              1/1     Running     0          8m59s
   openwhisk-invoker-0                           1/1     Running     0          60m
   openwhisk-kafka-0                             1/1     Running     0          60m
   openwhisk-kafkaprovider-78f8494b7d-9krhh      1/1     Running     0          60m
   openwhisk-nginx-5475965bfb-mt44p              1/1     Running     0          60m
   openwhisk-redis-7f8f844b4b-nncpm              1/1     Running     0          60m
   openwhisk-wskadmin                            1/1     Running     0          60m
   openwhisk-zookeeper-0                         1/1     Running     0          60m
   wskopenwhisk-invoker-00-1-prewarm-nodejs10    1/1     Running     0          57m
   wskopenwhisk-invoker-00-2-prewarm-nodejs10    1/1     Running     0          57m
   
   $ kubectl logs openwhisk-install-packages-kczns -n openwhisk
   Cloning into 'openwhisk'...
   /openwhisk /
   Note: checking out '9bef49fcd47f7922e4226ff7a97385f1313f7d64'.
   
   You are in 'detached HEAD' state. You can look around, make experimental
   changes and commit them, and you can discard any commits you make in this
   state without impacting any branches by performing another checkout.
   
   If you want to create a new branch to retain commits you create, you may
   do so (now or later) by using -b with the checkout command again. Example:
   
     git checkout -b <new-branch-name>
   
   HEAD is now at 9bef49fc KCF: propagate cf_ca_extraArgs_env_i into user containers (#4570)
   /
   /openwhisk/ansible/roles/routemgmt/files /
   Installing apimgmt package
   error: Package update failed: The connection failed, or timed out. (HTTP status code 502)
   Failed to deploy routemgmt package; will pause, uninstall, and try again
   Deleting routemgmt actions
   error: Unable to get action 'routemgmt/getApi': The connection failed, or timed out. (HTTP status code 502)
   Run 'wsk --help' for usage.
   error: Unable to get action 'routemgmt/createApi': The connection failed, or timed out. (HTTP status code 502)
   Run 'wsk --help' for usage.
   error: Unable to get action 'routemgmt/deleteApi': The connection failed, or timed out. (HTTP status code 502)
   Run 'wsk --help' for usage.
   Deleting routemgmt package - but only if it exists
   error: Unable to get package 'routemgmt': The connection failed, or timed out. (HTTP status code 502)
   Deleting apimgmt actions
   error: Unable to get action 'apimgmt/getApi': The connection failed, or timed out. (HTTP status code 502)
   Run 'wsk --help' for usage.
   error: Unable to get action 'apimgmt/createApi': The connection failed, or timed out. (HTTP status code 502)
   Run 'wsk --help' for usage.
   error: Unable to get action 'apimgmt/deleteApi': The connection failed, or timed out. (HTTP status code 502)
   Run 'wsk --help' for usage.
   Deleting apimgmt package - but only if it exists
   error: Unable to get package 'apimgmt': The connection failed, or timed out. (HTTP status code 502)
   
   $ kubectl logs openwhisk-nginx-5475965bfb-mt44p -n openwhisk
   2019/08/26 06:24:36 [error] 6#6: recv() failed (111: Connection refused) while resolving, resolver: 23.217.138.108:53
   2019/08/26 06:24:41 [error] 6#6: *1 openwhisk-controller.openwhisk.svc.cluster.local could not be resolved (110: Operation timed out), client: 10.233.104.0, server: ~^(?<namespace>[0-9a-zA-Z-]+)\.192.168.56.120$, request: "PUT /api/v1/namespaces/whisk.system/packages/apimgmt?overwrite=true HTTP/1.1", host: "192.168.56.120:31001"
   2019/08/26 06:25:01 [error] 6#6: recv() failed (111: Connection refused) while resolving, resolver: 23.217.138.108:53
   2019/08/26 06:25:21 [error] 6#6: *4 openwhisk-controller.openwhisk.svc.cluster.local could not be resolved (110: Operation timed out), client: 10.233.104.0, server: ~^(?<namespace>[0-9a-zA-Z-]+)\.192.168.56.120$, request: "GET /api/v1/namespaces/whisk.system/actions/routemgmt/getApi?code=false HTTP/1.1", host: "192.168.56.120:31001"
   2019/08/26 06:25:51 [error] 6#6: *5 openwhisk-controller.openwhisk.svc.cluster.local could not be resolved (110: Operation timed out), client: 10.233.104.0, server: ~^(?<namespace>[0-9a-zA-Z-]+)\.192.168.56.120$, request: "GET /api/v1/namespaces/whisk.system/actions/routemgmt/createApi?code=false HTTP/1.1", host: "192.168.56.120:31001"
   2019/08/26 06:26:21 [error] 6#6: *6 openwhisk-controller.openwhisk.svc.cluster.local could not be resolved (110: Operation timed out), client: 10.233.104.0, server: ~^(?<namespace>[0-9a-zA-Z-]+)\.192.168.56.120$, request: "GET /api/v1/namespaces/whisk.system/actions/routemgmt/deleteApi?code=false HTTP/1.1", host: "192.168.56.120:31001"
   2019/08/26 06:26:51 [error] 6#6: *7 openwhisk-controller.openwhisk.svc.cluster.local could not be resolved (110: Operation timed out), client: 10.233.104.0, server: ~^(?<namespace>[0-9a-zA-Z-]+)\.192.168.56.120$, request: "GET /api/v1/namespaces/whisk.system/packages/routemgmt HTTP/1.1", host: "192.168.56.120:31001"
   2019/08/26 06:27:07 [error] 6#6: recv() failed (111: Connection refused) while resolving, resolver: 23.202.231.167:53
   2019/08/26 06:27:21 [error] 6#6: *8 openwhisk-controller.openwhisk.svc.cluster.local could not be resolved (110: Operation timed out), client: 10.233.104.0, server: ~^(?<namespace>[0-9a-zA-Z-]+)\.192.168.56.120$, request: "GET /api/v1/namespaces/whisk.system/actions/apimgmt/getApi?code=false HTTP/1.1", host: "192.168.56.120:31001"
   2019/08/26 06:27:27 [error] 6#6: recv() failed (111: Connection refused) while resolving, resolver: 23.217.138.108:53
   2019/08/26 06:27:42 [error] 6#6: recv() failed (111: Connection refused) while resolving, resolver: 23.202.231.167:53
   2019/08/26 06:27:51 [error] 6#6: *9 openwhisk-controller.openwhisk.svc.cluster.local could not be resolved (110: Operation timed out), client: 10.233.104.0, server: ~^(?<namespace>[0-9a-zA-Z-]+)\.192.168.56.120$, request: "GET /api/v1/namespaces/whisk.system/actions/apimgmt/createApi?code=false HTTP/1.1", host: "192.168.56.120:31001"
   2019/08/26 06:28:07 [error] 6#6: recv() failed (111: Connection refused) while resolving, resolver: 23.202.231.167:53
   
   $ cat owcluster.yaml
   whisk:
     ingress:
        type: NodePort
        apiHostName: 192.168.56.120
        apiHostPort: 31001
   nginx:
     httpsNodePort: 31001
   
   invoker:
     containerFactory:
       impl: "kubernetes"
   
   k8s:
     persistence:
       enabled: false
   
   $ kubectl get nodes -o wide
   NAME       STATUS   ROLES    AGE   VERSION   INTERNAL-IP      EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
   controlz   Ready    master   11d   v1.15.2   192.168.56.120   <none>        Ubuntu 18.04.2 LTS   4.15.0-54-generic   docker://18.9.7
   node01     Ready    <none>   11d   v1.15.2   192.168.56.121   <none>        Ubuntu 18.04.2 LTS   4.15.0-54-generic   docker://18.9.7
   node02     Ready    <none>   11d   v1.15.2   192.168.56.122   <none>        Ubuntu 18.04.2 LTS   4.15.0-54-generic   docker://18.9.7
   
   
   
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services