-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.19.0
-
Important
-
None
-
Proposed
-
False
-
Description of problem:
Cannot use DNS name to check connectivity to clusterIP service on BGP
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. create backend pod and svc in ns3
$ oc get pods -owide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES hello-pod-1 1/1 Running 0 12m 10.131.2.41 openshift-qe-025.lab.eng.rdu2.redhat.com <none> <none> $ oc get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE test-service ClusterIP 172.30.19.176 <none> 27017/TCP 12m
2. check connectivity using svcIP
$ oc exec hello-pod-1 -- curl --connect-timeout 5 -s 172.30.19.176:27017 Hello OpenShift!
3. check connectivity using svc DNS name
$ oc exec hello-pod-1 -- curl --connect-timeout 5 -s http://test-service.ns3.svc:27017
command terminated with exit code 6
Actual results:
connectivity using svc DNS name failed
Expected results:
connectivity using svc DNS name should work
