helm install fails on local k8s
- Dominant language
- Scala
- Stars
- 6.8k
- Forks
- 1.2k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 2
Description
## Environment details:
Local k8s cluster on Linux
## Steps to reproduce the issue:
Followed the instructions to install local with ```helm```
```mycluster.yaml``` used:
```
whisk:
ingress:
type: NodePort
apiHostName: localhost
apiHostPort: 31001
useInternally: false
nginx:
httpsNodePort: 31001
# A single node cluster; so disable affinity
affinity:
enabled: false
toleration:
enabled: false
invoker:
options: "-Dwhisk.kubernetes.user-pod-node-affinity.enabled=false"
containerFactory:
impl: "kubernetes"
```
## Provide the actual results and outputs:
```
NAME READY STATUS RESTARTS AGE
owdev-alarmprovider-6bf4cdd68c-sbnpf 1/1 Running 2 (29m ago) 28h
owdev-apigateway-644688857f-gj55k 1/1 Running 2 (29m ago) 28h
owdev-controller-0 1/1 Running 2 (29m ago) 28h
owdev-couchdb-555b6d8ff4-xbjh7 1/1 Running 2 (29m ago) 28h
owdev-gen-certs-zbzqh 0/1 Completed 0 28h
owdev-init-couchdb-7gx6f 0/1 Completed 0 28h
owdev-install-packages-f84xt 0/1 Error 0 28h
owdev-install-packages-qlmdt 0/1 Error 0 28h
owdev-install-packages-qqlzr 0/1 Error 0 25h
owdev-install-packages-ttk2m 0/1 Unknown 0 28h
owdev-invoker-0 1/1 Running 2 (29m ago) 28h
owdev-kafka-0 1/1 Running 2 (29m ago) 28h
owdev-kafkaprovider-5785cbb579-6wgq4 1/1 Running 2 (29m ago) 28h
owdev-nginx-6c7448668b-vthv2 1/1 Running 2 (29m ago) 28h
owdev-redis-848f56f555-qzbpx 1/1 Running 2 (29m ago) 28h
owdev-tests-package-checker 0/1 Error 0 7m28s
owdev-wskadmin 1/1 Running 2 (29m ago) 28h
owdev-zookeeper-0 1/1 Running 2 (29m ago) 28h
wskowdev-invoker-00-1-prewarm-nodejs10 1/1 Running 0 27m
wskowdev-invoker-00-2-prewarm-nodejs10 1/1 Running 0 27m
```
```owdev-install-packages-*``` all failed.
Logs from the pods look like this:
```
Defaulted container "install-packages" out of: install-packages, wait-for-healthy-invoker (init)
Cloning into 'openwhisk'...
/openwhisk /
Note: checking out '1.0.0'.
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
HEAD is now at 2c621c07 fix start.sh to work on macos (#5019)
/
/openwhisk/ansible/roles/routemgmt/files /
Installing apimgmt package
error: Package update failed: Put https://localhost:31001/api/v1/namespaces/whisk.system/packages/apimgmt?overwrite=true: dial tcp [::1]:31001: getsockopt: connection refused
Failed to deploy routemgmt package; will pause, uninstall, and try again
Deleting routemgmt actions
error: Unable to get action 'routemgmt/getApi': Get https://localhost:31001/api/v1/namespaces/whisk.system/actions/routemgmt/getApi?code=false: dial tcp [::1]:31001: getsockopt: connection refused
Run 'wsk --help' for usage.
error: Unable to get action 'routemgmt/createApi': Get https://localhost:31001/api/v1/namespaces/whisk.system/actions/routemgmt/createApi?code=false: dial tcp [::1]:31001: getsockopt: connection refused
Run 'wsk --help' for usage.
error: Unable to get action 'routemgmt/deleteApi': Get https://localhost:31001/api/v1/namespaces/whisk.system/actions/routemgmt/deleteApi?code=false: dial tcp [::1]:31001: getsockopt: connection refused
Run 'wsk --help' for usage.
Deleting routemgmt package - but only if it exists
error: Unable to get package 'routemgmt': Get https://localhost:31001/api/v1/namespaces/whisk.system/packages/routemgmt: dial tcp [::1]:31001: getsockopt: connection refused
Deleting apimgmt actions
error: Unable to get action 'apimgmt/getApi': Get https://localhost:31001/api/v1/namespaces/whisk.system/actions/apimgmt/getApi?code=false: dial tcp [::1]:31001: getsockopt: connection refused
Run 'wsk --help' for usage.
error: Unable to get action 'apimgmt/createApi': Get https://localhost:31001/api/v1/namespaces/whisk.system/actions/apimgmt/createApi?code=false: dial tcp [::1]:31001: getsockopt: connection refused
Run 'wsk --help' for usage.
```
If I use ```apiHostName: 127.0.0.1``` it still errors out.
```
Installing apimgmt package
error: Package update failed: Put https://127.0.0.1:31001/api/v1/namespaces/whisk.system/packages/apimgmt?overwrite=true: dial tcp 127.0.0.1:31001: getsockopt: connection refused
Failed to deploy routemgmt package; will pause, uninstall, and try again
Deleting routemgmt actions
error: Unable to get action 'routemgmt/getApi': Get https://127.0.0.1:31001/api/v1/namespaces/whisk.system/actions/routemgmt/getApi?code=false: dial tcp 127.0.0.1:31001: getsockopt: connection refused
Run 'wsk --help' for usage.
error: Unable to get action 'routemgmt/createApi': Get https://127.0.0.1:31001/api/v1/namespaces/whisk.system/actions/routemgmt/createApi?code=false: dial tcp 127.0.0.1:31001: getsockopt: connection refused
Run 'wsk --help' for usage.
error: Unable to get action 'routemgmt/deleteApi': Get https://127.0.0.1:31001/api/v1/namespaces/whisk.system/actions/routemgmt/deleteApi?code=false: dial tcp 127.0.0.1:31001: getsockopt: connection refused
Run 'wsk --help' for usage.
Deleting routemgmt package - but only if it exists
error: Unable to get package 'routemgmt': Get https://127.0.0.1:31001/api/v1/namespaces/whisk.system/packages/routemgmt: dial tcp 127.0.0.1:31001: getsockopt: connection refused
Deleting apimgmt actions
# and so on...
```
Contributor guide
Research direction
Start with the Helm deployment using mycluster.yaml and inspect the owdev-install-packages-* pod logs. Trace how whisk.ingress.apiHostName, apiHostPort, and nginx.httpsNodePort are used for the package installation request, then reproduce the connection-refused failure on the local Kubernetes cluster. Done means the install-packages jobs can reach the configured API endpoint and complete successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, linux
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100