extended tests failing to clean up namespaces

[smarterclayton]

Extended.deploymentconfigs with multiple image change triggers [Conformance] should run a successful deployment with multiple triggers

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/10128/testReport/junit/(root)/Extended/deploymentconfigs_with_multiple_image_change_triggers__Conformance__should_run_a_successful_deployment_with_multiple_triggers/

/data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:142
Jan 13 13:50:55.401: Couldn't delete ns: "extended-test-cli-deployment-dgf3x-j2rk0": namespace extended-test-cli-deployment-dgf3x-j2rk0 was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed (&errors.errorString{s:"namespace extended-test-cli-deployment-dgf3x-j2rk0 was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed"})
/data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:353

@derekwaynecarr

[smarterclayton]

Isn't there an upstream report of this in 1.5?

[smarterclayton]

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_gce/151/testReport/junit/(root)/Extended/_k8s_io__Kubectl_client__k8s_io__Kubectl_run_pod_should_create_a_pod_from_an_image_when_restart_is_Never__Conformance_/

[derekwaynecarr]

My memory from 1.5 is that this has been relatively reliable, last major issue was related to pods not getting deleted....

[derekwaynecarr]

There are a couple incidences of this against 1.5 upstream:
kubernetes/kubernetes#40391

The incidence is not super frequent, I think the priority should be reduced to match upstream.

[0xmichalis]

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install_update/1063/testReport/junit/(root)/Extended/deploymentconfigs_when_run_iteratively__Conformance__should_immediately_start_a_new_deployment/

[soltysh]

Another one in https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/1070/testReport/junit/(root)/Extended/deploymentconfigs_with_enhanced_status__Conformance__should_include_various_info_in_status/

[smarterclayton]

I'm going to increase to 10 workers like upstream after discussion with @liggitt

…

On Wed, Jun 21, 2017 at 11:32 AM, Maciej Szulik ***@***.***> wrote: Another one in https://ci.openshift.redhat.com/jenkins/job/merge_pull_ request_origin/1070/testReport/junit/(root)/Extended/deploymentconfigs_ with_enhanced_status__Conformance__should_include_various_info_in_status/ — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#12487 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABG_pyhOT5YvmDhAvoknXZBLFOydf2Zqks5sGTeGgaJpZM4LjVty> .

[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

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close