Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intermittent 404s during TestScaleTo10 #2681

Closed
mattmoor opened this issue Dec 9, 2018 · 0 comments
Closed

Intermittent 404s during TestScaleTo10 #2681

mattmoor opened this issue Dec 9, 2018 · 0 comments
Labels
area/networking area/test-and-release It flags unit/e2e/conformance/perf test issues for product features kind/bug Categorizes issue or PR as related to a bug.

Comments

@mattmoor
Copy link
Member

mattmoor commented Dec 9, 2018

e.g. here:

scale_test.go:125: Route "scale-00010-005-quvtpcyb.serving-tests.example.com" prober failed with error: Get unexpected response &{404 Not Found 404 map[Date:[Sun, 09 Dec 2018 18:25:14 GMT] Server:[envoy] Content-Length:[0] Zipkin_trace_id:[734fefe365b6f665e9da511df2a7d3e7]] []}

I suspect that this is caused by the following:

  • We have a gateway with N > 1 replicas,
  • The new network config rolls out to M < N replicas,
  • WaitForEndpointState hits one of the M replicas, and
  • The route probes hit one of the N-M replicas

I believe the original workaround for this was this, where we ran a single gateway.

I suspect that we should have this for both gateways like we have here.

However, this workaround breaks down for scale testing, where we may need N replicas to reach a certain scale...

cc @alculquicondor @tcnghia

@knative-prow-robot knative-prow-robot added area/networking area/test-and-release It flags unit/e2e/conformance/perf test issues for product features kind/bug Categorizes issue or PR as related to a bug. labels Dec 9, 2018
mattmoor added a commit that referenced this issue Dec 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking area/test-and-release It flags unit/e2e/conformance/perf test issues for product features kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants