Extended.[networking][router] weighted openshift router The HAProxy router should appropriately serve a route that points to two services

[bparees]

/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/router/weighted.go:110
Expected error:
    <*errors.errorString | 0xc421ebe040>: {
        s: "last response from server was not 200:\n",
    }
    last response from server was not 200:
    
not to have occurred
/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/router/weighted.go:72

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance_future/427/testReport/junit/(root)/Extended/_networking__router__weighted_openshift_router_The_HAProxy_router_should_appropriately_serve_a_route_that_points_to_two_services/

[bparees]

it's possible this is not a flake but rather a failure introduced by #13001

[bparees]

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance_future/699/

[smarterclayton]

I found a bug last night in these tests - we were actually pulling the image, which meant that most of the tests were timed out on waiting for pull. we were pulling the wrong image as well, which #13388 fixes. So this should get better, but the real problem is:

We need to pre pull images.

[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