Description of problem:
pod failed to communicate to itself
Version-Release number of selected component (if applicable):
Server Version: 4.3.5
pod to itself communication was failing with connection timeout.
* connect to 172.30.x.x port 80 failed: Connection timed out
Steps to Reproduce:
Setting the target to 4.5. We will make backport decisions once the bug is understood.
Tested this issue on 4.3.0-0.nightly-2020-04-20-084750, this should be working, see:
$oc create -f list_for_pods.json
$ oc get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
test-service ClusterIP 172.30.113.135 <none> 27017/TCP 5s
$ oc get pod
NAME READY STATUS RESTARTS AGE
test-rc-5ql59 1/1 Running 0 9s
test-rc-8b77h 1/1 Running 0 9s
$ oc rsh test-rc-5ql59
~ $ curl test-service:27017
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.