nerdguru commented on issue #229: Upon helm execution "an error occurred forwarding 39967 -> 44134" URL: https://github.com/apache/incubator-openwhisk-deploy-kube/issues/229#issuecomment-400810481 Sorry it took me a couple of days to get back to this, but I wiped my NUK (and bare metal may be my problem as we'll soon see) with Ubuntu 16.04 and started from scratch, but got similar results. Version info: `# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial # docker version Client: Version: 1.13.1 API version: 1.26 Go version: go1.6.2 Git commit: 092cba3 Built: Thu Nov 2 20:40:23 2017 OS/Arch: linux/amd64 Server: Version: 1.13.1 API version: 1.26 (minimum version 1.12) Go version: go1.6.2 Git commit: 092cba3 Built: Thu Nov 2 20:40:23 2017 OS/Arch: linux/amd64 Experimental: false # kubectl version Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T21:07:38Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"", Minor:"", GitVersion:"v1.9.4", GitCommit:"bee2d1505c4fe820744d26d41ecd3fdd4a3d6546", GitTreeState:"clean", BuildDate:"2018-03-21T21:48:36Z", GoVersion:"go1.9.1", Compiler:"gc", Platform:"linux/amd64"} # minikube version minikube version: v0.25.2 ` As advised, I started following this: https://medium.com/openwhisk/deploying-openwhisk-on-kubernetes-3f55f781fbab but made Ubuntu substitutions as needed for things like installing asdf. I launched minikube with: ``` # minikube start --vm-driver=none There is a newer version of minikube available (v0.28.0). Download it here: https://github.com/kubernetes/minikube/releases/tag/v0.28.0 To disable this notification, run the following: minikube config set WantUpdateNotification false Starting local Kubernetes v1.9.4 cluster... Starting VM... Getting VM IP address... Moving files into cluster... Downloading localkube binary 163.02 MB / 163.02 MB [============================================] 100.00% 0s 0 B / 65 B [----------------------------------------------------------] 0.00% 65 B / 65 B [======================================================] 100.00% 0sSetting up certs... Connecting to cluster... Setting up kubeconfig... Starting cluster components... Kubectl is now configured to use the cluster. ``` When I get to the OpenWhisk install, I see a similar error to before: ``` # helm install . --namespace=openwhisk -f mycluster.yaml E0627 12:56:26.552804 18126 portforward.go:331] an error occurred forwarding 42989 -> 44134: error forwarding port 44134 to pod 08edc78aca326c3168069b3cc9f4235a5c2dce034cb9286a7a1b67f80e1c1d25, uid : unable to do port forwarding: socat not found. ``` Here's the running pods: ``` # kubectl get pods -n kube-systemNAME READY STATUS RESTARTS AGE kube-addon-manager-k8s 1/1 Running 0 3h kube-dns-54cccfbdf8-n886f 3/3 Running 0 3h kubernetes-dashboard-77d8b98585-tj8hv 1/1 Running 0 3h storage-provisioner 1/1 Running 0 3h tiller-deploy-7ccf99cd64-wkhjg 1/1 Running 0 3h ``` So, cleaner install than last time and DNS is healthy, unlike before. Thoughts? The no-vm driver maybe and I need to try this on a VM instead of bare metal?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on 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
