TEST-INFRA: [CI] Git clone fails due to TLS handshake error #1638

Closed
opened 2026-04-02 23:21:16 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: fix/ci-git-clone-tls-handshake-error
  • Commit Message: fix(ci): resolve TLS handshake error causing git clone failure
  • Milestone: v3.2.0
  • Parent Epic: #401

Description

The git clone command fails with a TLS handshake error, even when SSL verification is disabled. This prevents any analysis of the repository. The error message is: gnutls_handshake() failed: The server name sent was not recognized. This is likely a server-side configuration issue with SNI.

Subtasks

  • Reproduce the TLS handshake error in a controlled CI environment
  • Investigate server-side SNI configuration for the git host
  • Determine whether the issue is in the CI runner's TLS client or the server's SNI response
  • Apply fix (e.g., correct SNI hostname, update TLS configuration, or adjust CI runner network settings)
  • Verify git clone succeeds in CI after the fix
  • Confirm no regression in other CI jobs that perform git operations

Definition of Done

  • git clone completes successfully in CI without TLS errors
  • The root cause (SNI misconfiguration or client-side TLS issue) is documented
  • Fix is applied and verified across all affected CI jobs
  • All nox stages pass
  • Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

## Metadata - **Branch**: `fix/ci-git-clone-tls-handshake-error` - **Commit Message**: `fix(ci): resolve TLS handshake error causing git clone failure` - **Milestone**: v3.2.0 - **Parent Epic**: #401 ## Description The git clone command fails with a TLS handshake error, even when SSL verification is disabled. This prevents any analysis of the repository. The error message is: `gnutls_handshake() failed: The server name sent was not recognized`. This is likely a server-side configuration issue with SNI. ## Subtasks - [ ] Reproduce the TLS handshake error in a controlled CI environment - [ ] Investigate server-side SNI configuration for the git host - [ ] Determine whether the issue is in the CI runner's TLS client or the server's SNI response - [ ] Apply fix (e.g., correct SNI hostname, update TLS configuration, or adjust CI runner network settings) - [ ] Verify git clone succeeds in CI after the fix - [ ] Confirm no regression in other CI jobs that perform git operations ## Definition of Done - [ ] `git clone` completes successfully in CI without TLS errors - [ ] The root cause (SNI misconfiguration or client-side TLS issue) is documented - [ ] Fix is applied and verified across all affected CI jobs - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
freemo added this to the v3.2.0 milestone 2026-04-02 23:21:46 +00:00
Author
Owner

Closing as duplicate of #1543. This TLS/clone failure is already tracked as Priority/Critical, MoSCoW/Must Have.


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Closing as duplicate of #1543. This TLS/clone failure is already tracked as Priority/Critical, MoSCoW/Must Have. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
freemo 2026-04-02 23:30:28 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#1638
No description provided.