istio: Regression: istio.io egress test case gets 408 instead of 504

(NOTE: This is used to report product bugs: To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities To ask questions about how to use Istio, please visit https://discuss.istio.io)

Bug description

Running the tasks/traffic-management/egress/egress-control test and it is failing. Specifically, the tests for this section: https://istio.io/latest/docs/tasks/traffic-management/egress/egress-control/#manage-traffic-to-external-services. This section says the test should go from a 2002 to a 504 return code, and instead we are getting back a 408.

VERIFY FAILED snip_manage_traffic_to_external_services_3 (timeout after 120s):
received:
"408
real	0m 3.02s
user	0m 0.00s
sys	0m 0.00s"
expected:
"504
real    0m3.149s
user    0m0.004s
sys     0m0.004s"

I’m not sure if this is a regression, or a desired. If the later, we can update the docs.

[ ] Docs [ ] Installation [x] Networking [ ] Performance and Scalability [ ] Extensions and Telemetry [ ] Security [ ] Test and Release [ ] User Experience [ ] Developer Infrastructure [ ] Upgrade

Expected behavior

Existing tests should continue to pass

Steps to reproduce the bug

Run the istio.io test. See https://github.com/istio/istio.io/tree/master/tests.

Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)

Latest master

How was Istio installed?

Via pipeline

Environment where the bug was observed (cloud vendor, OS, etc)

Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue. Refer cluster state archive for more details.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 29 (27 by maintainers)

Most upvoted comments

Ok. I found the issue - It is in Envoy. The new Envoy when timeout happens is returning 408 instead of 504. I have asked the question here https://github.com/envoyproxy/envoy/pull/15585#issuecomment-824155470 - Let us wait for what Envoy folks say and decide accordingly.

I’m hoping that it would get back ported to the https://github.com/envoyproxy/envoy/tree/release/v1.18 branch. At that point, we would pick the change up within 24 hrs and be in our builds. Then not sure if we need something else in istio/istio. Once this happens, the istio.io test should fail when picking up the istio build, and require a change in the test to use 504 instead of 408.

Even if we merge something like https://github.com/istio/istio.io/pull/9356, please keep this open as a release blocker until ^ is answered