cleveragents/cleveragents-core

Fork 3

TEST-INFRA: Unable to access repository files for CI pipeline analysis #1656

New issue

Closed

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

freemo commented

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

Owner

Metadata

Branch: fix/test-infra-repo-access-tls-sni
Commit Message: fix(infra): resolve TLS/SNI handshake failure blocking CI pipeline analysis
Milestone: v3.7.0
Parent Epic: (orphan — needs manual linking, see comment below)

Background and Context

During CI pipeline design analysis for the cleveragents-core repository, the test infrastructure agent is unable to clone the repository or read files via the Forgejo API. This is a blocking issue that prevents any meaningful CI pipeline analysis, design, or implementation work from proceeding.

The root cause appears to be a TLS/SNI (Server Name Indication) handshake failure when attempting to connect to the Forgejo host. The server does not recognise the server name sent during the TLS negotiation, causing all git clone and API file-read operations to fail.

Current Behavior

All attempts to clone the repository or access files via the API fail with the following error:

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

This error occurs when:

Running git clone against the repository URL
Attempting to read files via the Forgejo REST API
Any operation that requires establishing a TLS connection to the Forgejo host

As a result, the CI pipeline design analysis cannot be completed — no source files, workflow configurations, or test infrastructure can be inspected.

Expected Behavior

git clone of the cleveragents/cleveragents-core repository completes successfully.
Files are accessible via the Forgejo API without TLS/SNI errors.
CI pipeline analysis can proceed unblocked.

Acceptance Criteria

The TLS/SNI configuration on the Forgejo host is corrected so that the server name is recognised during handshake.
git clone https://<host>/cleveragents/cleveragents-core.git succeeds without TLS errors.
Forgejo API file-read endpoints return 200 OK responses (not TLS errors).
CI pipeline analysis work (blocked by this issue) can resume.

Supporting Information

Related infrastructure issue: #1543 (fix(infra): resolve TLS handshake failure on git.dev.cleveragents.com blocking repository clone)
Related issue: #1629 (TEST-INFRA: Git repository is inaccessible due to TLS/SNI error)
Related issue: #1630 (TEST-INFRA: [ci-pipeline-design] Unable to clone repository due to TLS/SNI issue)

Subtasks

Investigate TLS/SNI configuration on the Forgejo host (git.cleverthis.com)
Identify whether the issue is a missing/mismatched SSL certificate SAN or a server-side SNI routing misconfiguration
Apply the appropriate fix (certificate renewal, SNI routing correction, or reverse-proxy reconfiguration)
Verify git clone succeeds from the CI runner environment
Verify Forgejo API file-read endpoints are accessible
Confirm CI pipeline analysis work is unblocked
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.
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.
All nox stages pass.
Coverage >= 97%.

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

## Metadata - **Branch**: `fix/test-infra-repo-access-tls-sni` - **Commit Message**: `fix(infra): resolve TLS/SNI handshake failure blocking CI pipeline analysis` - **Milestone**: v3.7.0 - **Parent Epic**: _(orphan — needs manual linking, see comment below)_ ## Background and Context During CI pipeline design analysis for the `cleveragents-core` repository, the test infrastructure agent is unable to clone the repository or read files via the Forgejo API. This is a blocking issue that prevents any meaningful CI pipeline analysis, design, or implementation work from proceeding. The root cause appears to be a TLS/SNI (Server Name Indication) handshake failure when attempting to connect to the Forgejo host. The server does not recognise the server name sent during the TLS negotiation, causing all git clone and API file-read operations to fail. ## Current Behavior All attempts to clone the repository or access files via the API fail with the following error: ``` gnutls_handshake() failed: The server name sent was not recognized ``` This error occurs when: - Running `git clone` against the repository URL - Attempting to read files via the Forgejo REST API - Any operation that requires establishing a TLS connection to the Forgejo host As a result, the CI pipeline design analysis cannot be completed — no source files, workflow configurations, or test infrastructure can be inspected. ## Expected Behavior - `git clone` of the `cleveragents/cleveragents-core` repository completes successfully. - Files are accessible via the Forgejo API without TLS/SNI errors. - CI pipeline analysis can proceed unblocked. ## Acceptance Criteria - [ ] The TLS/SNI configuration on the Forgejo host is corrected so that the server name is recognised during handshake. - [ ] `git clone https://<host>/cleveragents/cleveragents-core.git` succeeds without TLS errors. - [ ] Forgejo API file-read endpoints return `200 OK` responses (not TLS errors). - [ ] CI pipeline analysis work (blocked by this issue) can resume. ## Supporting Information - Related infrastructure issue: #1543 (`fix(infra): resolve TLS handshake failure on git.dev.cleveragents.com blocking repository clone`) - Related issue: #1629 (`TEST-INFRA: Git repository is inaccessible due to TLS/SNI error`) - Related issue: #1630 (`TEST-INFRA: [ci-pipeline-design] Unable to clone repository due to TLS/SNI issue`) ## Subtasks - [ ] Investigate TLS/SNI configuration on the Forgejo host (`git.cleverthis.com`) - [ ] Identify whether the issue is a missing/mismatched SSL certificate SAN or a server-side SNI routing misconfiguration - [ ] Apply the appropriate fix (certificate renewal, SNI routing correction, or reverse-proxy reconfiguration) - [ ] Verify `git clone` succeeds from the CI runner environment - [ ] Verify Forgejo API file-read endpoints are accessible - [ ] Confirm CI pipeline analysis work is unblocked - [ ] 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. - 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**. - All nox stages pass. - Coverage >= 97%. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

freemo added this to the v3.7.0 milestone

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

freemo commented

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

Author

Owner

⚠️ Orphan Issue — Manual Linking Required

This issue was created automatically but no parent Epic or Legendary issue could be identified in the repository for the TEST-INFRA / CI pipeline domain.

Per CONTRIBUTING.md, every issue must be linked to a parent Epic using Forgejo's dependency system (child blocks parent). Please manually:

Identify or create the appropriate parent Type/Epic or Type/Legendary issue for Test Infrastructure / CI pipeline work.
Link this issue as a child by adding a blocks dependency from this issue (#1656) to the parent Epic.

Related issues that may share a parent Epic:

#1629 — TEST-INFRA: Git repository is inaccessible due to TLS/SNI error
#1630 — TEST-INFRA: [ci-pipeline-design] Unable to clone repository due to TLS/SNI issue
#1543 — fix(infra): resolve TLS handshake failure on git.dev.cleveragents.com

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

⚠️ **Orphan Issue — Manual Linking Required** This issue was created automatically but **no parent Epic or Legendary issue** could be identified in the repository for the `TEST-INFRA` / CI pipeline domain. Per `CONTRIBUTING.md`, every issue must be linked to a parent Epic using Forgejo's dependency system (child **blocks** parent). Please manually: 1. Identify or create the appropriate parent `Type/Epic` or `Type/Legendary` issue for Test Infrastructure / CI pipeline work. 2. Link this issue as a child by adding a **blocks** dependency from this issue (#1656) to the parent Epic. Related issues that may share a parent Epic: - #1629 — `TEST-INFRA: Git repository is inaccessible due to TLS/SNI error` - #1630 — `TEST-INFRA: [ci-pipeline-design] Unable to clone repository due to TLS/SNI issue` - #1543 — `fix(infra): resolve TLS handshake failure on git.dev.cleveragents.com` --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

freemo commented

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

closed this issue
added the
State
Duplicate
label

freemo commented

2026-04-02 23:33:43 +00:00

Author

Owner

Closing as duplicate of #1543. Issue #1543 is the canonical tracking issue for the TLS/git-clone failure. 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 is the canonical tracking issue for the TLS/git-clone failure. Multiple issues have been filed about the same underlying TLS configuration problem. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

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:40:27 +00:00

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

freemo referenced this issue

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

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