Extended.idling and unidling unidling should work with TCP (when fully idled)

[knobunc]

------------------------------
idling and unidling unidling 
  should work with TCP (when fully idled) [Conformance]
  /data/src/github.com/openshift/origin/test/extended/idling/idling.go:309

STEP: Creating a kubernetes client
Sep  1 14:31:46.435: INFO: >>> kubeConfig: /tmp/openshift/openshift/test-extended/core/openshift.local.config/master/admin.kubeconfig

STEP: Building a namespace api object
Sep  1 14:31:46.479: INFO: configPath is now "/tmp/openshift/extended-test-cli-idling-r87sd-xpgny-user.kubeconfig"
Sep  1 14:31:46.479: INFO: The user is now "extended-test-cli-idling-r87sd-xpgny-user"
Sep  1 14:31:46.479: INFO: Creating project "extended-test-cli-idling-r87sd-xpgny"
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Building a namespace api object
Sep  1 14:31:47.020: INFO: configPath is now "/tmp/openshift/extended-test-cli-idling-r87sd-cvgex-user.kubeconfig"
Sep  1 14:31:47.020: INFO: The user is now "extended-test-cli-idling-r87sd-cvgex-user"
Sep  1 14:31:47.020: INFO: Creating project "extended-test-cli-idling-r87sd-cvgex"
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Creating the resources
Sep  1 14:31:47.389: INFO: Running 'oc create --namespace=extended-test-cli-idling-r87sd-cvgex --config=/tmp/openshift/extended-test-cli-idling-r87sd-cvgex-user.kubeconfig -f /data/src/github.com/openshift/origin/test/extended/testdata/idling-echo-server.yaml -o name'
STEP: Creating the idling file
STEP: Waiting for the endpoints to exist
STEP: Waiting for endpoints to be up
STEP: Idling the service
Sep  1 14:32:19.027: INFO: Running 'oc idle --namespace=extended-test-cli-idling-r87sd-cvgex --config=/tmp/openshift/extended-test-cli-idling-r87sd-cvgex-user.kubeconfig --resource-names-file /tmp/openshift/openshift-extended-tests/idling-services-246870143'
STEP: Waiting for the pods to have terminated
STEP: Connecting to the service IP and checking the echo
STEP: Collecting resource usage data
Sep  1 14:32:36.302: INFO: Closed stop channel. Waiting for 1 workers
Sep  1 14:32:36.302: INFO: Closing worker for 172.18.0.100
Sep  1 14:32:36.302: INFO: Waitgroup finished.
Sep  1 14:32:36.302: INFO: Unknown output type: . Skipping.
Sep  1 14:32:36.302: INFO: Waiting up to 1m0s for all nodes to be ready
STEP: Destroying namespace "extended-test-cli-idling-r87sd-xpgny" for this suite.
STEP: Destroying namespace "extended-test-cli-idling-r87sd-cvgex" for this suite.
STEP: Cleaning up the idling file


• Failure [74.984 seconds]
idling and unidling
/data/src/github.com/openshift/origin/test/extended/idling/idling.go:466
  unidling
  /data/src/github.com/openshift/origin/test/extended/idling/idling.go:465
    should work with TCP (when fully idled) [Conformance] [It]
    /data/src/github.com/openshift/origin/test/extended/idling/idling.go:309

    Expected error:
        <*errors.errorString | 0xc82101c1e0>: {
            s: "unable to read data from echo server for service idling-echo: read tcp 172.18.0.100:55154->172.30.12.10:8675: read: connection reset by peer",
        }
        unable to read data from echo server for service idling-echo: read tcp 172.18.0.100:55154->172.30.12.10:8675: read: connection reset by peer
    not to have occurred

    /data/src/github.com/openshift/origin/test/extended/idling/idling.go:297
------------------------------

As seen in:
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/5823/consoleText

[0xmichalis]

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/7012/consoleFull

[bparees]

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install/1832/consoleFull#-163316032756cbb9a5e4b02b88ae8c2f77

[smarterclayton]

https://ci.openshift.redhat.com/jenkins/job/test_branch_origin/639/testReport/junit/(root)/Extended/idling_and_unidling_unidling_should_work_with_TCP__when_fully_idled___Conformance___local_/

New symptom. Can we actually try and fix this. The number of times it has failed are ridiculous

[soltysh]

Another one https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install_update/901/consoleFull

[bparees]

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install_update/1590/

[bparees]

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/3104/

[stevekuznetsov]

@knobunc @DirectXMan12 @derekwaynecarr looks like a suggest for this was discussed in March above: #10773 (comment)

What is the status on this? I know other underlying issues are bubbling up as failures for this test but this has been by far the most flaky test we have ever had in our suites and I would really love to see it get nailed down for good.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[stevekuznetsov]

Kind of amazing this stopped flaking out.

/close

[bparees]

Kind of amazing this stopped flaking out.

sssshhh..you'll wake the beast.