titan/ariadne
3
0
Fork 0
Code Issues 140 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

[hermes] ariadne #546: transient_infra_failure #17

New Issue
Open
opened 2026-09-27 18:20:49 +00:00 by hermes-automation · 0 comments
hermes-automation commented 2026-09-27 18:20:49 +00:00
Member
Copy Link

Hermes auto-triage classified incident ariadne/546 as transient_infra_failure (confidence 0.92); first failed gate: scm_checkout.

Why a human is needed

Build 546 never reached the repository's code. The timer-triggered run failed during the initial Jenkinsfile checkout: git fetch against https://scm.bstein.dev/titan/ariadne.git aborted with 'Error in the HTTP2 framing layer', a transport-level HTTP/2 protocol error between the Jenkins git client and the Git host, and Jenkins gave up after exhausting its checkout retries, so no stage, test, or quality gate ever ran. No change to this repository is needed: re-running the same commit should pass once the connection path to the Git host is healthy. If the error recurs across builds, the fix belongs on the Git client or the proxy in front of the Git host (for example, forcing HTTP/1.1 for this remote), not in this codebase.

Ariadne did not authorize automated remediation: evidence_signature_missing.

Facts

  • jenkins — Jenkins build ariadne #546 was started by timer at 2026-09-27T17:06:00Z and finished FAILURE at 2026-09-27T17:08:25Z after 144 seconds. (https://ci.bstein.dev/job/ariadne/546/ (timestamps, result))
  • jenkins — The build failed while fetching the repository to read the Jenkinsfile: the command 'git fetch --tags --force --progress -- https://scm.bstein.dev/titan/ariadne.git +refs/heads/:refs/remotes/origin/' returned status code 128 with stderr 'fatal: unable to access https://scm.bstein.dev/titan/aria... (console_failures[0] at line 13; hudson.plugins.git.GitException in console_tail)
  • jenkins — Jenkins exhausted its checkout retries ('ERROR: Maximum checkout retry attempts reached, aborting') and ended the build; no pipeline stage ever ran and jenkins.first_failed_stage is null. (console_tail; jenkins.first_failed_stage)
  • jenkins — No test results were published for this build: jenkins.failed_tests is empty, consistent with the build failing before any code was checked out or executed. (jenkins.failed_tests)
  • opensearch — Correlated application log evidence is unavailable for this incident: the OpenSearch query for 2026-09-27T17:01:00Z to 17:13:25Z failed with 'opensearch request failed: [Errno 111] Connection refused' and returned no records. (log_evidence.error, log_evidence.records)

Evidence

The earliest failure region of the build console:

	at PluginClassLoader for git//hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1239)
	at PluginClassLoader for git//hudson.plugins.git.GitSCM._checkout(GitSCM.java:1310)
	at PluginClassLoader for git//hudson.plugins.git.GitSCM.checkout(GitSCM.java:1277)
	at PluginClassLoader for workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136)
	at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:168)
	at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:70)
	at PluginClassLoader for workflow-job//org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:317)
	at hudson.model.ResourceController.execute(ResourceController.java:101)
	at hudson.model.Executor.run(Executor.java:460)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- https://scm.bstein.dev/titan/ariadne.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: unable to access 'https://scm.bstein.dev/titan/ariadne.git/': Error in the HTTP2 framing layer
... (truncated; the full log is in the linked build)

Inferences

  • 'Error in the HTTP2 framing layer' is the git/curl HTTP/2 protocol error: the connection to scm.bstein.dev was established (credentials were resolved and the fetch began), but the HTTP/2 stream was corrupted or dropped mid-transfer, which most commonly points at a reverse proxy or ingress in fron...
  • Because the run was timer-triggered on the same branch and failed before checkout completed, re-running the same commit is expected to succeed once the connection path to the Git host is healthy.
  • If this framing error recurs across builds, a durable fix would be to make the Jenkins git client use HTTP/1.1 for this remote (git config http.version HTTP/1.1 on the controller/agents) or to review HTTP/2 stream handling on the proxy in front of scm.bstein.dev; a single occurrence does not indi...

Links

  • Failed build: https://ci.bstein.dev/job/ariadne/546/
  • Full evidence bundle and audit trail live in Ariadne at /api/admin/audit/events, event types hermes_autotriage_incident and hermes_autotriage_diagnosis.

Filed automatically by Ariadne from a Hermes Agent diagnosis (run run_db7151ed84934f6d870285a7fc2506bc). Hermes has no write access to this repository; no files or infrastructure were changed.

Hermes auto-triage classified incident `ariadne/546` as **transient_infra_failure** (confidence 0.92); first failed gate: `scm_checkout`. ## Why a human is needed Build 546 never reached the repository's code. The timer-triggered run failed during the initial Jenkinsfile checkout: git fetch against https://scm.bstein.dev/titan/ariadne.git aborted with 'Error in the HTTP2 framing layer', a transport-level HTTP/2 protocol error between the Jenkins git client and the Git host, and Jenkins gave up after exhausting its checkout retries, so no stage, test, or quality gate ever ran. No change to this repository is needed: re-running the same commit should pass once the connection path to the Git host is healthy. If the error recurs across builds, the fix belongs on the Git client or the proxy in front of the Git host (for example, forcing HTTP/1.1 for this remote), not in this codebase. Ariadne did not authorize automated remediation: `evidence_signature_missing`. ## Facts - **jenkins** — Jenkins build ariadne #546 was started by timer at 2026-09-27T17:06:00Z and finished FAILURE at 2026-09-27T17:08:25Z after 144 seconds. (`https://ci.bstein.dev/job/ariadne/546/ (timestamps, result)`) - **jenkins** — The build failed while fetching the repository to read the Jenkinsfile: the command 'git fetch --tags --force --progress -- https://scm.bstein.dev/titan/ariadne.git +refs/heads/*:refs/remotes/origin/*' returned status code 128 with stderr 'fatal: unable to access https://scm.bstein.dev/titan/aria... (`console_failures[0] at line 13; hudson.plugins.git.GitException in console_tail`) - **jenkins** — Jenkins exhausted its checkout retries ('ERROR: Maximum checkout retry attempts reached, aborting') and ended the build; no pipeline stage ever ran and jenkins.first_failed_stage is null. (`console_tail; jenkins.first_failed_stage`) - **jenkins** — No test results were published for this build: jenkins.failed_tests is empty, consistent with the build failing before any code was checked out or executed. (`jenkins.failed_tests`) - **opensearch** — Correlated application log evidence is unavailable for this incident: the OpenSearch query for 2026-09-27T17:01:00Z to 17:13:25Z failed with 'opensearch request failed: [Errno 111] Connection refused' and returned no records. (`log_evidence.error, log_evidence.records`) ## Evidence The earliest failure region of the build console: ``` at PluginClassLoader for git//hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1239) at PluginClassLoader for git//hudson.plugins.git.GitSCM._checkout(GitSCM.java:1310) at PluginClassLoader for git//hudson.plugins.git.GitSCM.checkout(GitSCM.java:1277) at PluginClassLoader for workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136) at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:168) at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:70) at PluginClassLoader for workflow-job//org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:317) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:460) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- https://scm.bstein.dev/titan/ariadne.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: unable to access 'https://scm.bstein.dev/titan/ariadne.git/': Error in the HTTP2 framing layer ... (truncated; the full log is in the linked build) ``` ## Inferences - 'Error in the HTTP2 framing layer' is the git/curl HTTP/2 protocol error: the connection to scm.bstein.dev was established (credentials were resolved and the fetch began), but the HTTP/2 stream was corrupted or dropped mid-transfer, which most commonly points at a reverse proxy or ingress in fron... - Because the run was timer-triggered on the same branch and failed before checkout completed, re-running the same commit is expected to succeed once the connection path to the Git host is healthy. - If this framing error recurs across builds, a durable fix would be to make the Jenkins git client use HTTP/1.1 for this remote (git config http.version HTTP/1.1 on the controller/agents) or to review HTTP/2 stream handling on the proxy in front of scm.bstein.dev; a single occurrence does not indi... ## Links - Failed build: https://ci.bstein.dev/job/ariadne/546/ - Full evidence bundle and audit trail live in Ariadne at `/api/admin/audit/events`, event types `hermes_autotriage_incident` and `hermes_autotriage_diagnosis`. Filed automatically by Ariadne from a Hermes Agent diagnosis (run [run_db7151ed84934f6d870285a7fc2506bc](https://triage.bstein.dev/chat?resume=run_db7151ed84934f6d870285a7fc2506bc)). Hermes has no write access to this repository; no files or infrastructure were changed. <!-- hermes-triage job=ariadne classification=transient_infra_failure incident=ariadne/546 -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
atlas-reconciler bstein hermes-automation
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: titan/ariadne#17
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?