SDN test should wait longer for namespaces

[smarterclayton]

Flaking heavily in master

[openshift-merge-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smarterclayton

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

• test/integration/OWNERS [smarterclayton]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[smarterclayton]

@deads2k integration is continually flaking, this is extracted from my integration refactor where it stomped that

[openshift-ci-robot]

@smarterclayton: The following tests failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/openshift-jenkins/extended_conformance_gce	dbd7e47	link	/test extended_conformance_gce
ci/openshift-jenkins/end_to_end	dbd7e47	link	/test end_to_end
ci/openshift-jenkins/extended_conformance_install_update	dbd7e47	link	/test extended_conformance_install_update
ci/openshift-jenkins/extended_templates	dbd7e47	link	/test extended_templates

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[smarterclayton]

e2e failed building images but didn't exit: #15702

[smarterclayton]

Passed integration. Force merging.

[deads2k]

@deads2k integration is continually flaking, this is extracted from my integration refactor where it stomped that

You think that non-parallel it takes more than two seconds to observe a create?

[smarterclayton]

Fairly sure - but the retry logic is not properly printing out the second run logs correctly.

…

On Wed, Aug 9, 2017 at 12:32 PM, David Eads ***@***.***> wrote: @deads2k <https://github.com/deads2k> integration is continually flaking, this is extracted from my integration refactor where it stomped that You think that non-parallel it takes more than two seconds to observe a create? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#15700 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABG_pzzUIE3n5EfVCtXzuM93mqHqGqM0ks5sWd8dgaJpZM4OyLPM> .

[danwinship]

You think that non-parallel it takes more than two seconds to observe a create?

It's not just failing to observe the creation of the newly-created namespace. It doesn't even observe the existence of "default". Maybe something is causing startup of the shared informer to be unexpectedly slow?

[deads2k]

It's not just failing to observe the creation of the newly-created namespace. It doesn't even observe the existence of "default". Maybe something is causing startup of the shared informer to be unexpectedly slow?

Hard to believe that would happen just this informer/handler pair and never another or at least not to anything approaching the same degree

[smarterclayton]

Note that some of the runs were from before the fix to the start hook landed. I'm still watching for the second set of hooks.

…

On Wed, Aug 9, 2017 at 1:39 PM, David Eads ***@***.***> wrote: It's not just failing to observe the creation of the newly-created namespace. It doesn't even observe the existence of "default". Maybe something is causing startup of the shared informer to be unexpectedly slow? Hard to believe that would happen just *this* informer/handler pair and never another or at least not to anything approaching the same degree — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#15700 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABG_p0U31T_Fsii5q-R6Hz4MPMbF0DArks5sWe7bgaJpZM4OyLPM> .

[smarterclayton]

Might be a hook init failure: https://storage.googleapis.com/origin-ci-test/pr-logs/pull/15248/test_pull_request_origin_integration/5706/build-log.txt or could be the latent flake we have in project watch test. After this merged I saw no more oadmpodnetwork flakes.