titan/soteria
3
0
Fork 0
Code Issues 87 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

[hermes] soteria #740: transient_infra_failure #30

New Issue
Open
opened 2026-09-22 06:39:31 +00:00 by hermes-automation · 0 comments
hermes-automation commented 2026-09-22 06:39:31 +00:00
Member
Copy Link

Hermes auto-triage classified incident soteria/740 as transient_infra_failure (confidence 0.99); first failed gate: SCM checkout to retrieve Jenkinsfile, before pipeline execution.

Why a human is needed

Jenkins could not fetch the Soteria repository to load Jenkinsfile because scm.bstein.dev returned HTTP 500. Checkout retries were exhausted before any pipeline tests ran. Re-run the same commit once the SCM endpoint is responding normally; if the error persists, investigate the SCM service and its upstream dependencies rather than changing Soteria code or test expectations.

Ariadne did not authorize automated remediation: evidence_signature_missing.

Facts

  • jenkins — Jenkins was checking out https://scm.bstein.dev/titan/soteria.git into its Soteria@script workspace to read Jenkinsfile when the failure occurred. (Attached Ariadne bundle: jenkins.console_tail, opening checkout message; https://ci.bstein.dev/job/soteria/740/)
  • jenkins — The earliest detected failure region shows git fetch exiting with status 128 because the SCM endpoint returned HTTP 500. (Attached Ariadne bundle: jenkins.console_failures[0], marker at line 18, nested GitException and stderr: 'The requested URL returned error: 500')
  • jenkins — Jenkins exhausted checkout retries and aborted. Asset publication was subsequently skipped, and the build finished FAILURE. (Attached Ariadne bundle: jenkins.console_failures[0].text, 'Maximum checkout retry attempts reached, aborting' and subsequent messages)
  • jenkins — The bundle reports no named failed pipeline stage and contains no structured failed-test results. (Attached Ariadne bundle: jenkins.first_failed_stage=null; jenkins.failed_tests=[])
  • opensearch — Supplementary OpenSearch evidence could not be collected because its request was refused; no log records were returned. (Attached Ariadne bundle: log_evidence.error='opensearch request failed: [Errno 111] Connection refused'; 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/soteria.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: unable to access 'https://scm.bstein.dev/titan/soteria.git/': The requested URL returned error: 5
... (truncated; the full log is in the linked build)

Inferences

  • The build failed during Jenkinsfile retrieval, before pipeline stages or repository tests could execute. This is not evidence of a Soteria source or test regression.
  • The HTTP 500 indicates a failure on the SCM serving path. The bundle does not establish whether Gitea itself or an intermediary generated that response, nor whether the problem has since cleared.
  • Retrying the same commit after the SCM endpoint recovers is the appropriate recovery; no repository change is indicated. The separate OpenSearch connection refusal does not establish a shared cause.

Links

  • Failed build: https://ci.bstein.dev/job/soteria/740/
  • 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_ea734c5629d3436ba1e93b2dbe841ffb). Hermes has no write access to this repository; no files or infrastructure were changed.

Hermes auto-triage classified incident `soteria/740` as **transient_infra_failure** (confidence 0.99); first failed gate: `SCM checkout to retrieve Jenkinsfile, before pipeline execution`. ## Why a human is needed Jenkins could not fetch the Soteria repository to load Jenkinsfile because scm.bstein.dev returned HTTP 500. Checkout retries were exhausted before any pipeline tests ran. Re-run the same commit once the SCM endpoint is responding normally; if the error persists, investigate the SCM service and its upstream dependencies rather than changing Soteria code or test expectations. Ariadne did not authorize automated remediation: `evidence_signature_missing`. ## Facts - **jenkins** — Jenkins was checking out https://scm.bstein.dev/titan/soteria.git into its Soteria@script workspace to read Jenkinsfile when the failure occurred. (`Attached Ariadne bundle: jenkins.console_tail, opening checkout message; https://ci.bstein.dev/job/soteria/740/`) - **jenkins** — The earliest detected failure region shows git fetch exiting with status 128 because the SCM endpoint returned HTTP 500. (`Attached Ariadne bundle: jenkins.console_failures[0], marker at line 18, nested GitException and stderr: 'The requested URL returned error: 500'`) - **jenkins** — Jenkins exhausted checkout retries and aborted. Asset publication was subsequently skipped, and the build finished FAILURE. (`Attached Ariadne bundle: jenkins.console_failures[0].text, 'Maximum checkout retry attempts reached, aborting' and subsequent messages`) - **jenkins** — The bundle reports no named failed pipeline stage and contains no structured failed-test results. (`Attached Ariadne bundle: jenkins.first_failed_stage=null; jenkins.failed_tests=[]`) - **opensearch** — Supplementary OpenSearch evidence could not be collected because its request was refused; no log records were returned. (`Attached Ariadne bundle: log_evidence.error='opensearch request failed: [Errno 111] Connection refused'; 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/soteria.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: unable to access 'https://scm.bstein.dev/titan/soteria.git/': The requested URL returned error: 5 ... (truncated; the full log is in the linked build) ``` ## Inferences - The build failed during Jenkinsfile retrieval, before pipeline stages or repository tests could execute. This is not evidence of a Soteria source or test regression. - The HTTP 500 indicates a failure on the SCM serving path. The bundle does not establish whether Gitea itself or an intermediary generated that response, nor whether the problem has since cleared. - Retrying the same commit after the SCM endpoint recovers is the appropriate recovery; no repository change is indicated. The separate OpenSearch connection refusal does not establish a shared cause. ## Links - Failed build: https://ci.bstein.dev/job/soteria/740/ - 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_ea734c5629d3436ba1e93b2dbe841ffb](https://triage.bstein.dev/chat?resume=run_ea734c5629d3436ba1e93b2dbe841ffb)). Hermes has no write access to this repository; no files or infrastructure were changed. <!-- hermes-triage job=soteria classification=transient_infra_failure incident=soteria/740 -->
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/soteria#30
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?