TEST-INFRA: [ci-pipeline-design] Git clone fails with gnutls_handshake error #1592

Closed
opened 2026-04-02 23:01:06 +00:00 by freemo · 3 comments
Owner

Metadata

  • Branch: fix/ci-git-clone-gnutls-handshake-error
  • Commit Message: fix(ci): resolve gnutls_handshake TLS failure blocking git clone in CI pipeline
  • Milestone: v3.8.0
  • Parent Epic: (orphan — no ci-pipeline-design Epic found; requires manual linking)

Background and Context

The CI pipeline relies on cloning the cleveragents/cleveragents-core repository as a prerequisite for automated analysis and modification tasks. A TLS/SNI misconfiguration on git.cleveragents.com prevents this operation from succeeding, blocking all downstream automated workflows.

Current Behavior (for Bugs)

When attempting to clone the cleveragents/cleveragents-core repository, the command fails with the following error:

Cloning into '/tmp/ca-test-infra-...'...
fatal: unable to access 'https://git.cleveragents.com/cleveragents/cleveragents-core.git/': gnutls_handshake() failed: The server name sent was not recognized

This error occurs even when disabling SSL verification using git -c http.sslVerify=false clone ....

This is a blocking issue that prevents any automated analysis or modification of the repository.

Expected Behavior

The git clone https://git.cleveragents.com/cleveragents/cleveragents-core.git command completes successfully without any TLS/SSL errors, allowing CI pipeline steps to proceed normally.

Acceptance Criteria

  • The repository can be cloned successfully without any TLS/SSL errors from git.cleveragents.com
  • The SSL certificate is correctly configured and includes the git.cleveragents.com hostname (SNI)
  • The server correctly handles SNI requests for git.cleveragents.com
  • CI pipeline steps that depend on git clone are unblocked and pass

Supporting Information

  • Related issue: #1532 — BUG-HUNT: [Infrastructure] TLS Configuration Error on git.cleveragents.com
  • Related issue: #1543 — fix(infra): resolve TLS handshake failure on git.dev.cleveragents.com
  • Related issue: #1541 — TEST-INFRA: [ci-pipeline-design] Unable to push to repository

Subtasks

  • Investigate the server configuration for git.cleveragents.com
  • Ensure the SSL certificate is correctly configured and supports the domain name (SNI)
  • Verify that the server is correctly handling SNI requests
  • Test git clone succeeds from the CI runner environment
  • Run nox and fix any errors

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off.
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
  • All nox stages pass
  • Coverage >= 97%

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

## Metadata - **Branch**: `fix/ci-git-clone-gnutls-handshake-error` - **Commit Message**: `fix(ci): resolve gnutls_handshake TLS failure blocking git clone in CI pipeline` - **Milestone**: v3.8.0 - **Parent Epic**: *(orphan — no ci-pipeline-design Epic found; requires manual linking)* ## Background and Context The CI pipeline relies on cloning the `cleveragents/cleveragents-core` repository as a prerequisite for automated analysis and modification tasks. A TLS/SNI misconfiguration on `git.cleveragents.com` prevents this operation from succeeding, blocking all downstream automated workflows. ## Current Behavior (for Bugs) When attempting to clone the `cleveragents/cleveragents-core` repository, the command fails with the following error: ``` Cloning into '/tmp/ca-test-infra-...'... fatal: unable to access 'https://git.cleveragents.com/cleveragents/cleveragents-core.git/': gnutls_handshake() failed: The server name sent was not recognized ``` This error occurs even when disabling SSL verification using `git -c http.sslVerify=false clone ...`. This is a blocking issue that prevents any automated analysis or modification of the repository. ## Expected Behavior The `git clone https://git.cleveragents.com/cleveragents/cleveragents-core.git` command completes successfully without any TLS/SSL errors, allowing CI pipeline steps to proceed normally. ## Acceptance Criteria - [ ] The repository can be cloned successfully without any TLS/SSL errors from `git.cleveragents.com` - [ ] The SSL certificate is correctly configured and includes the `git.cleveragents.com` hostname (SNI) - [ ] The server correctly handles SNI requests for `git.cleveragents.com` - [ ] CI pipeline steps that depend on `git clone` are unblocked and pass ## Supporting Information - Related issue: #1532 — BUG-HUNT: [Infrastructure] TLS Configuration Error on git.cleveragents.com - Related issue: #1543 — fix(infra): resolve TLS handshake failure on git.dev.cleveragents.com - Related issue: #1541 — TEST-INFRA: [ci-pipeline-design] Unable to push to repository ## Subtasks - [ ] Investigate the server configuration for `git.cleveragents.com` - [ ] Ensure the SSL certificate is correctly configured and supports the domain name (SNI) - [ ] Verify that the server is correctly handling SNI requests - [ ] Test `git clone` succeeds from the CI runner environment - [ ] Run `nox` and fix any errors ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the **Commit Message** in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. - All nox stages pass - Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
freemo added this to the v3.8.0 milestone 2026-04-02 23:01:10 +00:00
Author
Owner

⚠️ Orphan Issue — Manual Linking Required

No parent Epic was found for the ci-pipeline-design category. All other TEST-INFRA: [ci-pipeline-design] issues (e.g., #1535, #1536, #1537, #1538, #1539, #1540, #1541) are also currently orphaned with no parent Epic.

Per CONTRIBUTING.md, orphan issues are not permitted. A Type/Epic issue covering CI pipeline design and test infrastructure improvements should be created, and this issue should be linked as a child (this issue blocks the parent Epic).

The closest candidate parent Epics in the existing hierarchy are:

  • #376 — Legendary: Hardening, Testing & Security (covers test infrastructure)
  • #739 — Epic: E2E Testing Suite for Acceptance Criteria and Workflow Examples

Action required: Create a ci-pipeline-design Epic and link this issue as a child blocker.


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

⚠️ **Orphan Issue — Manual Linking Required** No parent Epic was found for the `ci-pipeline-design` category. All other `TEST-INFRA: [ci-pipeline-design]` issues (e.g., #1535, #1536, #1537, #1538, #1539, #1540, #1541) are also currently orphaned with no parent Epic. Per CONTRIBUTING.md, orphan issues are **not permitted**. A `Type/Epic` issue covering CI pipeline design and test infrastructure improvements should be created, and this issue should be linked as a child (this issue **blocks** the parent Epic). The closest candidate parent Epics in the existing hierarchy are: - **#376** — Legendary: Hardening, Testing & Security (covers test infrastructure) - **#739** — Epic: E2E Testing Suite for Acceptance Criteria and Workflow Examples **Action required**: Create a `ci-pipeline-design` Epic and link this issue as a child blocker. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
Author
Owner

Closing as duplicate of #1543.

This issue reports the same gnutls_handshake clone failure that is already tracked in #1543 (Priority/Critical, MoSCoW/Must Have, v3.7.0). All work should be consolidated there.


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

Closing as duplicate of #1543. This issue reports the same gnutls_handshake clone failure that is already tracked in #1543 (Priority/Critical, MoSCoW/Must Have, v3.7.0). All work should be consolidated there. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
freemo 2026-04-02 23:16:51 +00:00
Author
Owner

Closing as duplicate of #1543. Issue #1543 (fix(infra): resolve TLS handshake failure on git.dev.cleveragents.io) is the canonical tracking issue for the TLS/git-clone failure, with MoSCoW/Must have, Priority/Critical, State/Verified labels. Multiple issues have been filed about the same underlying TLS configuration problem.


Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

Closing as duplicate of #1543. Issue #1543 (`fix(infra): resolve TLS handshake failure on git.dev.cleveragents.io`) is the canonical tracking issue for the TLS/git-clone failure, with `MoSCoW/Must have`, `Priority/Critical`, `State/Verified` labels. Multiple issues have been filed about the same underlying TLS configuration problem. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
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.

Dependencies

No dependencies set.

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