Skip to content

fix: detect connection reset as TLS error in test assertions#838

Merged
trepel merged 1 commit intoKuadrant:mainfrom
trepel:tls-cert-error-fix
Jan 9, 2026
Merged

fix: detect connection reset as TLS error in test assertions#838
trepel merged 1 commit intoKuadrant:mainfrom
trepel:tls-cert-error-fix

Conversation

@trepel
Copy link
Copy Markdown
Contributor

@trepel trepel commented Jan 8, 2026

Description

For some reason if using clusters outside RHT VPN (ARO, AWS, GCP) the error returned in response in ./testsuite/tests/singlecluster/gateway/tlspolicy/test_tls_policy_section_targeting_gateway.py is different than the test expects.

Changes

Add "Connection reset by peer" to TLS error detection in has_tls_error().

I am not sure whether "Connection reset by peer" could create false positives in other scenarios but most likely not, this method is used in 2 tests only.

Verification

./testsuite/tests/singlecluster/gateway/reconciliation/change_targetref/test_update_tlspolicy_target_ref.py
make testsuite/tests/singlecluster/gateway/tlspolicy/test_tls_policy_section_targeting_gateway.py

  • but you need to have a cluster outside RHT VPN to fully validate this. Given how small the modifications in the PR are I'd say eye review is sufficient and we will see whether this works in nightlies.

PR Title Guidelines (Conventional Commits)

Your PR title must follow the conventional commit format:

<type>[optional scope]: <description>

Examples:

  • feat: add rate limiting policy for gateways
  • feat(gateway): add rate limiting policy
  • fix(authorino): resolve authorization timeout issue
  • test: add tests for DNS policy reconciliation
  • docs: update installation guide

Allowed types:

  • feat - New feature
  • fix - Bug fix
  • docs - Documentation changes
  • style - Code style changes (formatting, no logic change)
  • refactor - Code refactoring
  • perf - Performance improvements
  • test - Adding or updating tests
  • build - Build system changes
  • ci - CI/CD changes
  • chore - Other changes (dependencies, tooling)
  • revert - Revert a previous commit

Optional scopes:

  • authorino, chore, ci, dns, docs, gateway, limitador, multicluster, perf, refactor, style, test, tls

@trepel trepel requested review from averevki and emmaaroche January 8, 2026 15:08
Signed-off-by: Tomas Repel <trepel@redhat.com>
@trepel trepel force-pushed the tls-cert-error-fix branch from a4761a5 to 02c8bc3 Compare January 8, 2026 15:17
Copy link
Copy Markdown
Contributor

@emmaaroche emmaaroche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Copy link
Copy Markdown
Contributor

@averevki averevki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Were these tests successful on outside-VPN clusters before, or is this a recent issue? Connection reset by peer errors looks like something that should be backoff-ed (?)

@trepel
Copy link
Copy Markdown
Contributor Author

trepel commented Jan 9, 2026

I don't think the tests were successful on the outside-VPN cluster before - at least not consistently. I think it keeps failing on this since the first RHCL GA release. It's not recent or anything like that.

@trepel trepel merged commit e0f94e6 into Kuadrant:main Jan 9, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants