cleveragents/cleveragents-core

Fork 3

TEST-INFRA: [ci-pipeline-design] Unable to clone repository #1651

New issue

Closed

opened 2026-04-02 23:23:24 +00:00 by freemo · 3 comments

freemo commented

2026-04-02 23:23:24 +00:00

Owner

Background and Context

The Test Infrastructure Improver agent is unable to clone the cleveragents/cleveragents-core repository due to a TLS/SNI issue. The error message is gnutls_handshake() failed: The server name sent was not recognized. This prevents any analysis of the test infrastructure and blocks all CI pipeline work that depends on repository access.

Current Behavior

When attempting to clone the repository, the git client receives a TLS handshake failure:

gnutls_handshake() failed: The server name sent was not recognized

This indicates the server at git.cleveragents.com is not returning a TLS certificate that matches the SNI (Server Name Indication) sent by the client.

Expected Behavior

The repository should be cloneable without TLS/SNI errors. The server at git.cleveragents.com should present a valid TLS certificate matching the requested hostname, allowing all CI agents and tooling to clone and interact with the repository normally.

Acceptance Criteria

git clone https://git.cleveragents.com/cleveragents/cleveragents-core completes successfully without TLS errors
The server at git.cleveragents.com presents a valid TLS certificate matching the SNI hostname
All CI pipeline jobs that depend on repository cloning are unblocked
No TLS/SNI handshake failures are observed in CI logs

Supporting Information

Error: gnutls_handshake() failed: The server name sent was not recognized
Affected host: git.cleveragents.com
Impact: Blocks all Test Infrastructure analysis and CI pipeline work

Metadata

Branch: fix/ci-tls-sni-clone-failure
Commit Message: fix(ci): resolve TLS/SNI handshake failure preventing repository clone
Milestone: v3.8.0
Parent Epic: (orphan — no TEST-INFRA ci-pipeline-design Epic found; requires manual linking)

Subtasks

Investigate TLS/SNI configuration on git.cleveragents.com
Verify the server certificate covers the correct hostname(s)
Apply server-side fix (certificate renewal/reconfiguration or SNI routing fix)
Validate fix by successfully cloning the repository from a clean environment
Confirm CI pipeline jobs can clone the repository without errors
Run nox (all default sessions), fix any errors
Verify coverage >=97% via nox -s coverage_report

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

## Background and Context The Test Infrastructure Improver agent is unable to clone the `cleveragents/cleveragents-core` repository due to a TLS/SNI issue. The error message is `gnutls_handshake() failed: The server name sent was not recognized`. This prevents any analysis of the test infrastructure and blocks all CI pipeline work that depends on repository access. ## Current Behavior When attempting to clone the repository, the git client receives a TLS handshake failure: ``` gnutls_handshake() failed: The server name sent was not recognized ``` This indicates the server at `git.cleveragents.com` is not returning a TLS certificate that matches the SNI (Server Name Indication) sent by the client. ## Expected Behavior The repository should be cloneable without TLS/SNI errors. The server at `git.cleveragents.com` should present a valid TLS certificate matching the requested hostname, allowing all CI agents and tooling to clone and interact with the repository normally. ## Acceptance Criteria - [ ] `git clone https://git.cleveragents.com/cleveragents/cleveragents-core` completes successfully without TLS errors - [ ] The server at `git.cleveragents.com` presents a valid TLS certificate matching the SNI hostname - [ ] All CI pipeline jobs that depend on repository cloning are unblocked - [ ] No TLS/SNI handshake failures are observed in CI logs ## Supporting Information - Error: `gnutls_handshake() failed: The server name sent was not recognized` - Affected host: `git.cleveragents.com` - Impact: Blocks all Test Infrastructure analysis and CI pipeline work ## Metadata - **Branch**: `fix/ci-tls-sni-clone-failure` - **Commit Message**: `fix(ci): resolve TLS/SNI handshake failure preventing repository clone` - **Milestone**: v3.8.0 - **Parent Epic**: *(orphan — no TEST-INFRA ci-pipeline-design Epic found; requires manual linking)* ## Subtasks - [ ] Investigate TLS/SNI configuration on `git.cleveragents.com` - [ ] Verify the server certificate covers the correct hostname(s) - [ ] Apply server-side fix (certificate renewal/reconfiguration or SNI routing fix) - [ ] Validate fix by successfully cloning the repository from a clean environment - [ ] Confirm CI pipeline jobs can clone the repository without errors - [ ] Run `nox` (all default sessions), fix any errors - [ ] Verify coverage >=97% via `nox -s coverage_report` ## 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:23:46 +00:00

freemo commented

2026-04-02 23:24:50 +00:00

Author

Owner

⚠️ Orphan Issue — Manual Linking Required

This issue could not be automatically linked to a parent Epic. A search of all open issues with Type/Epic label returned 0 results, and no TEST-INFRA ci-pipeline-design Epic was found in the repository.

Per CONTRIBUTING.md, orphan issues are not permitted. A project owner must:

Create or identify the appropriate parent Epic for TEST-INFRA / ci-pipeline-design work
Link this issue as a child by making this issue block the parent Epic (child blocks parent direction)

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

⚠️ **Orphan Issue — Manual Linking Required** This issue could not be automatically linked to a parent Epic. A search of all open issues with `Type/Epic` label returned 0 results, and no TEST-INFRA ci-pipeline-design Epic was found in the repository. Per `CONTRIBUTING.md`, orphan issues are **not permitted**. A project owner must: 1. Create or identify the appropriate parent Epic for TEST-INFRA / ci-pipeline-design work 2. Link this issue as a child by making **this issue block the parent Epic** (child blocks parent direction) --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

freemo referenced this issue

2026-04-02 23:26:47 +00:00

GIT-INFRA: [BLOCKER] Git clone fails with TLS handshake error #1666

freemo referenced this issue

2026-04-02 23:28:19 +00:00

GIT-INFRA: [BLOCKER] Git clone fails with TLS handshake error #1666

freemo commented

2026-04-02 23:30:22 +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:22 +00:00

closed this issue
added the
State
Duplicate
label

freemo commented

2026-04-02 23:39:13 +00:00

Author

Owner

Closing as duplicate. This issue was marked State/Duplicate indicating it duplicates an existing TLS/repository clone failure issue. The canonical issue tracking this problem is #1532 (BUG-HUNT: TLS Configuration Error on git.cleveragents.com) and/or #1543 (fix(infra): resolve TLS handshake failure).

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

Closing as duplicate. This issue was marked `State/Duplicate` indicating it duplicates an existing TLS/repository clone failure issue. The canonical issue tracking this problem is #1532 (BUG-HUNT: TLS Configuration Error on git.cleveragents.com) and/or #1543 (fix(infra): resolve TLS handshake failure). --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

freemo referenced this issue

2026-04-02 23:55:03 +00:00

[Automated] Backlog Groomer Session State — v3.7.0 #1463