Move the failRateLimiting fail point to the ingress request rate limiter in session workflow

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Workload Resilience
    • Workload Resilience 2026-01-19, Workload Resilience 2026-02-02, Workload Resilience 2026-02-16, Workload Resilience 2026-03-02, Workload Resilience 2026-03-16
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Due to the lack of a dedicated port, we couldn't make a fail point that was acting just like the ingress request rate limiter. This is because background checks and critical commands like heartbeats would get caught too and would cause the test suite to fail.

      With the dedicated port, we can now add the random rejection at the session workflow level without rejecting critical commands or interfering with the background checks.

            Assignee:
            Blake Oler
            Reporter:
            Guillaume Racicot
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: