unclejack

PR #769 makes some improvements to make these tests faster and more reliable. PR #762 addresses some other issues which cause failures in these tests..

@jojimt The kubernetes cluster started by `CONTIV_K8=1 make k8s-sanity-cluster` doesn't seem healthy. Tests fail and pass at random. If the first tests have failed, the cluster needs to be shut...

build PR

@dseevr: I was checking to make sure the CI is ok. This needs to wait a bit longer.

I don't have the logs. I've seen them in the CI logs of a run. That run's CI logs are gone now because they get deleted automatically. I'll keep an...

I couldn't reproduce the failures I've seen on the CI. I'm fixing the issues directly.

A job on the CI has run into this failure: ``` time="2017-02-20T08:19:28Z" level=info msg="Output from rename: []" time="2017-02-20T08:19:28Z" level=info msg="Output from ip assign: []" time="2017-02-20T08:19:29Z" level=info msg="stat : Active Internet...

Here's another failure. This one is different. ``` FAIL: kubeClient_test.go:494: TestKube.TestKubeWatch --ADD-- Drv: &{numAddSvc:0 numDelSvc:0 numProvUpd:0 services:map[] providers:map[]} kubeClient_test.go:512: c.Errorf("Add service was not seen by client") ... Error: Add service...

This is still a problem.

I'm reopening this issue because I've seen it again on the CI.