molecule-ai/molecule-core
52
0
Fork 2
Code Issues 184 Pull Requests 27 Actions 18 Packages Projects Releases Wiki Activity

E2E teardown safety net broken #2914

New Issue
Closed
opened 2026-06-15 06:02:31 +00:00 by gitea-actions · 1 comment
gitea-actions bot commented 2026-06-15 06:02:31 +00:00
Copy Link
Copy Source

The weekly sanity run (E2E_INTENTIONAL_FAILURE=1) did not exit as expected. This means one of:

  • poisoning did not actually cause failure (test harness regression), OR
  • teardown left an orphan org (leak detection caught a real bug)

Run: https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/368865

This is higher priority than a canary failure — the whole E2E safety net cannot be trusted until this is resolved.

The weekly sanity run (E2E_INTENTIONAL_FAILURE=1) did not exit as expected. This means one of: - poisoning did not actually cause failure (test harness regression), OR - teardown left an orphan org (leak detection caught a real bug) Run: https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/368865 This is higher priority than a canary failure — the whole E2E safety net cannot be trusted until this is resolved.
agent-dev-a commented 2026-06-15 08:20:08 +00:00
Member
Copy Link
Copy Source

Investigated run 368865 / job 505463. The failure is NOT a harness regression or a teardown leak — the job exits with rc=2 because the admin token is rejected by staging CP (401 invalid admin auth token) before the harness can provision the org.

Root cause: secrets.CP_STAGING_ADMIN_API_TOKEN is either unset or stale in the org secret store. The workflow correctly detects an empty value and fails early; when the value is present-but-invalid, the workspace create call returns 401.

This is an operator/secret-rotation issue, not a code change. Once the secret is restored, the sanity run should resume its normal failure modes (rc=1 clean-failure or rc=4 leak).

Investigated run 368865 / job 505463. The failure is NOT a harness regression or a teardown leak — the job exits with rc=2 because the admin token is rejected by staging CP (`401 invalid admin auth token`) before the harness can provision the org. Root cause: `secrets.CP_STAGING_ADMIN_API_TOKEN` is either unset or stale in the org secret store. The workflow correctly detects an empty value and fails early; when the value is present-but-invalid, the workspace create call returns 401. This is an operator/secret-rotation issue, not a code change. Once the secret is restored, the sanity run should resume its normal failure modes (rc=1 clean-failure or rc=4 leak).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
approved
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 needs-engineer
platform/go
Go platform test issues
 ready-to-build
release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2914
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?