fix: detect connection reset as TLS error in test assertions#838
Merged
trepel merged 1 commit intoKuadrant:mainfrom Jan 9, 2026
Merged
fix: detect connection reset as TLS error in test assertions#838trepel merged 1 commit intoKuadrant:mainfrom
trepel merged 1 commit intoKuadrant:mainfrom
Conversation
Signed-off-by: Tomas Repel <trepel@redhat.com>
a4761a5 to
02c8bc3
Compare
averevki
reviewed
Jan 9, 2026
Contributor
averevki
left a comment
There was a problem hiding this comment.
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 (?)
Contributor
Author
|
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. |
averevki
approved these changes
Jan 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.pymake testsuite/tests/singlecluster/gateway/tlspolicy/test_tls_policy_section_targeting_gateway.pyPR Title Guidelines (Conventional Commits)
Your PR title must follow the conventional commit format:
Examples:
feat: add rate limiting policy for gatewaysfeat(gateway): add rate limiting policyfix(authorino): resolve authorization timeout issuetest: add tests for DNS policy reconciliationdocs: update installation guideAllowed types:
feat- New featurefix- Bug fixdocs- Documentation changesstyle- Code style changes (formatting, no logic change)refactor- Code refactoringperf- Performance improvementstest- Adding or updating testsbuild- Build system changesci- CI/CD changeschore- Other changes (dependencies, tooling)revert- Revert a previous commitOptional scopes:
authorino,chore,ci,dns,docs,gateway,limitador,multicluster,perf,refactor,style,test,tls