Bug 1801780 - unidling service does not work with ovn-kubernetes
Summary: unidling service does not work with ovn-kubernetes
Keywords:
Status: CLOSED DUPLICATE of bug 1785360
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-11 16:02 UTC by Weibin Liang
Modified: 2020-02-12 07:16 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-12 07:16:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Weibin Liang 2020-02-11 16:02:10 UTC
Description of problem:
unidling service does not work with ovn-kubernetes, but it works with openshift-sdn

Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-02-10-100932

How reproducible:
Always

Steps to Reproduce:
1. Create pods and service
2. from one pod to curl service:port, curl pass
3. oc idle above created service
4. from one pod to curl service:port, curl fail

[root@dhcp-41-193 FILE]# oc create -f https://raw.githubusercontent.com/anuragthehatter/v3-testfiles/master/networking/list_for_pods.json 
replicationcontroller/test-rc created
service/test-service created
[root@dhcp-41-193 FILE]# oc create -f https://raw.githubusercontent.com/anuragthehatter/v3-testfiles/master/networking/pod-for-ping.json 
pod/hello-pod created
[root@dhcp-41-193 FILE]# export KUBECONFIG=./kubeconfig1^C
[root@dhcp-41-193 FILE]# oc get all
NAME                READY   STATUS    RESTARTS   AGE
pod/hello-pod       1/1     Running   0          33s
pod/test-rc-bhl5n   1/1     Running   0          38s
pod/test-rc-kj29s   1/1     Running   0          38s

NAME                            DESIRED   CURRENT   READY   AGE
replicationcontroller/test-rc   2         2         2       39s

NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)     AGE
service/test-service   ClusterIP   172.30.73.146   <none>        27017/TCP   39s
[root@dhcp-41-193 FILE]# oc get ep
NAME           ENDPOINTS                           AGE
test-service   10.128.2.11:8080,10.131.0.17:8080   59s
[root@dhcp-41-193 FILE]# oc rsh hello-pod
/ # curl 172.30.73.146:27017
Hello OpenShift!
[root@dhcp-41-193 FILE]# oc idle test-service
The service "test/test-service" has been marked as idled 
The service will unidle ReplicationController "test/test-rc" to 2 replicas once it receives traffic 
ReplicationController "test/test-rc" has been idled 
[root@dhcp-41-193 FILE]# oc get ep
NAME           ENDPOINTS   AGE
test-service   <none>      72s
[root@dhcp-41-193 FILE]# oc rsh hello-pod
/ # curl 172.30.73.146:27017
curl: (7) Failed to connect to 172.30.73.146 port 27017: Operation timed out
/ # 

Actual results:
curl: (7) Failed to connect to 172.30.73.146 port 27017: Operation timed out

Expected results:
curl should pass

Additional info:

Comment 1 zhaozhanqi 2020-02-12 07:15:38 UTC
same issue with https://bugzilla.redhat.com/show_bug.cgi?id=1785360

Comment 2 zhaozhanqi 2020-02-12 07:16:21 UTC

*** This bug has been marked as a duplicate of bug 1785360 ***


Note You need to log in before you can comment on or make changes to this bug.