istio: istio.io tasks/traffic-management/locality-load-balancing/distribute test fails on the 1.9 branch

(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

Trying to move the istio.io tests from the release-1.8 branch to releasse-1.9 and the test now fails. The tail end of the log (https://storage.googleapis.com/istio-prow/pr-logs/pull/istio_istio.io/8562/doc.test.profile_default_istio.io/1351549967608582144/artifacts/tests-setup-profile-default-fdc/TestDocs/tasks/traffic-management/locality-load-balancing/distribute/test.sh/test.sh/_test_context/test.sh_output.txt:

Actual locality distribution:
region1.zone1: 36
region1.zone2: 32
region2.zone3: 0
region3.zone4: 32
Invalid locality distribution to region1.zone1: 36. Expected: 70

Affected product area (please put an X in all that apply)

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

Affected features (please put an X in all that apply)

[ ] Multi Cluster [ ] Virtual Machine [ ] Multi Control Plane

Expected behavior

Tests should pass

Steps to reproduce the bug

Run the istio.io test or try and follow the instructions on the content/en/docs/tasks/traffic-management/locality-load-balancing/distribute/index.md page.

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

1.0.0-beta.0 (currently)

How was Istio installed?

via test framework

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

Istio testing pipeline

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: 36 (36 by maintainers)

Most upvoted comments

@nmittler sure. Will take a look.