Bug 1991551

Description of problem:
Idle service cannot be waken up

Version-Release number of selected component (if applicable):
4.9.0-0.nightly-2021-08-07-175228

How reproducible:
always

Steps to Reproduce:

1. Create rc test pod and svc

$ oc create -f https://raw.githubusercontent.com/openshift/verification-tests/master/testdata/networking/list_for_pods.json
replicationcontroller/test-rc created
service/test-service created
$ oc get pod
NAME            READY   STATUS    RESTARTS   AGE
test-rc-bswdm   1/1     Running   0          4s
test-rc-p7hpg   1/1     Running   0          4s


2. Create another test pod

oc create -f https://raw.githubusercontent.com/openshift/verification-tests/master/testdata/networking/pod-for-ping.json


3. oc idle test-service


4. Access the idle service, can NOT be worked

$ oc exec -n ffcbg hello-pod -- curl 172.30.54.122:27017
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:06 --:--:--     0^C


5. check the ep

$ oc get ep -n ffcbg -o yaml
apiVersion: v1
items:
- apiVersion: v1
  kind: Endpoints
  metadata:
    annotations:
      idling.alpha.openshift.io/idled-at: "2021-08-09T11:52:34Z"
      idling.alpha.openshift.io/unidle-targets: '[{"kind":"ReplicationController","name":"test-rc","replicas":2}]'
    creationTimestamp: "2021-08-09T11:52:24Z"
    labels:
      name: test-service
    name: test-service
    namespace: ffcbg
    resourceVersion: "206036"
    uid: 7e2d6e4d-5a93-4922-9825-ace2fe442100
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

6. check the service

$ oc get svc -n ffcbg -o yaml
apiVersion: v1
items:
- apiVersion: v1
  kind: Service
  metadata:
    annotations:
      idling.alpha.openshift.io/idled-at: "2021-08-09T11:52:34Z"
      idling.alpha.openshift.io/unidle-targets: '[{"kind":"ReplicationController","name":"test-rc","replicas":2}]'
    creationTimestamp: "2021-08-09T11:52:24Z"
    labels:
      name: test-service
    name: test-service
    namespace: ffcbg
    resourceVersion: "206021"
    uid: 051fe7ee-23ef-451a-b32c-aaad8b687cb0
  spec:
    clusterIP: 172.30.54.122
    clusterIPs:
    - 172.30.54.122
    ipFamilies:
    - IPv4
    ipFamilyPolicy: SingleStack
    ports:
    - name: http
      port: 27017
      protocol: TCP
      targetPort: 8080
    selector:
      name: test-pods
    sessionAffinity: None
    type: ClusterIP
  status:
    loadBalancer: {}
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""


7. check the event

$ oc get event -n ffcbg
LAST SEEN   TYPE     REASON             OBJECT                          MESSAGE
5m26s       Normal   Scheduled          pod/hello-pod                   Successfully assigned ffcbg/hello-pod to ip-10-0-188-18.us-east-2.compute.internal
5m24s       Normal   AddedInterface     pod/hello-pod                   Add eth0 [10.131.0.57/23] from openshift-sdn
5m24s       Normal   Pulled             pod/hello-pod                   Container image "quay.io/openshifttest/hello-sdn@sha256:d5785550cf77b7932b090fcd1a2625472912fb3189d5973f177a5a2c347a1f95" already present on machine
5m24s       Normal   Created            pod/hello-pod                   Created container hello-pod
5m24s       Normal   Started            pod/hello-pod                   Started container hello-pod
5m41s       Normal   Scheduled          pod/test-rc-7vj5w               Successfully assigned ffcbg/test-rc-7vj5w to ip-10-0-215-184.us-east-2.compute.internal
5m39s       Normal   AddedInterface     pod/test-rc-7vj5w               Add eth0 [10.129.2.146/23] from openshift-sdn
5m39s       Normal   Pulled             pod/test-rc-7vj5w               Container image "quay.io/openshifttest/hello-sdn@sha256:d5785550cf77b7932b090fcd1a2625472912fb3189d5973f177a5a2c347a1f95" already present on machine
5m39s       Normal   Created            pod/test-rc-7vj5w               Created container test-pod
5m39s       Normal   Started            pod/test-rc-7vj5w               Started container test-pod
5m29s       Normal   Killing            pod/test-rc-7vj5w               Stopping container test-pod
5m41s       Normal   Scheduled          pod/test-rc-jqbl5               Successfully assigned ffcbg/test-rc-jqbl5 to ip-10-0-188-18.us-east-2.compute.internal
5m39s       Normal   AddedInterface     pod/test-rc-jqbl5               Add eth0 [10.131.0.56/23] from openshift-sdn
5m39s       Normal   Pulled             pod/test-rc-jqbl5               Container image "quay.io/openshifttest/hello-sdn@sha256:d5785550cf77b7932b090fcd1a2625472912fb3189d5973f177a5a2c347a1f95" already present on machine
5m39s       Normal   Created            pod/test-rc-jqbl5               Created container test-pod
5m39s       Normal   Started            pod/test-rc-jqbl5               Started container test-pod
5m29s       Normal   Killing            pod/test-rc-jqbl5               Stopping container test-pod
5m41s       Normal   SuccessfulCreate   replicationcontroller/test-rc   Created pod: test-rc-7vj5w
5m41s       Normal   SuccessfulCreate   replicationcontroller/test-rc   Created pod: test-rc-jqbl5
5m29s       Normal   SuccessfulDelete   replicationcontroller/test-rc   Deleted pod: test-rc-7vj5w
5m29s       Normal   SuccessfulDelete   replicationcontroller/test-rc   Deleted pod: test-rc-jqbl5

8.  check the iptables rule
sh-4.4# iptables-save | grep ffcbg
-A KUBE-PORTALS-CONTAINER -d 172.30.54.122/32 -p tcp -m comment --comment "ffcbg/test-service:http" -m tcp --dport 27017 -j REDIRECT --to-ports 35041
-A KUBE-PORTALS-HOST -d 172.30.54.122/32 -p tcp -m comment --comment "ffcbg/test-service:http" -m tcp --dport 27017 -j DNAT --to-destination 10.0.128.147:35041



Actual results:




Expected results:

access the svc can wake up the pods

Additional info: