Description of problem: Incorrect ip/network being choosen by port forward. An IP address should be choosen on the provisioning address. However the address that is being used is not on the correct network - the provisioning oc port-forward tiller-deploy-649959bd94-8bprm 44134:44134 error: error upgrading connection: unable to upgrade connection: error dialing backend: dial tcp 172.22.0.39:10010: connect: no route to host See version below Version-Release number of selected component (if applicable): [corona@bastion ~]$ oc version Client Version: openshift-clients-4.3.0-201910250623-88-g6a937dfe Server Version: 4.3.0 Kubernetes Version: v1.16.2 [corona@bastion ~]$ hostname bastion.stablcurco.vici.verizon.com Description of problem: Incorrect ip/network being choosen by port forward. An IP address should be choosen on the provisioning address. However the address that is being used is not on the correct network - the provisioning oc port-forward tiller-deploy-649959bd94-8bprm 44134:44134 error: error upgrading connection: unable to upgrade connection: error dialing backend: dial tcp 172.22.0.39:10010: connect: no route to host See version below Version-Release number of selected component (if applicable): [corona@bastion ~]$ oc version Client Version: openshift-clients-4.3.0-201910250623-88-g6a937dfe Server Version: 4.3.0 Kubernetes Version: v1.16.2 [corona@bastion ~]$ hostname bastion.stablcurco.vici.verizon.com How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
If you use the --address option for port-forward and set it to the right node IP address, does that make it work?
If your machine has multiple addresses one is chosen base on alphabetical order. You have the --address option to explicitly specify one, if the default picked is not the desired one.