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

main RED: Local Provision Lifecycle E2E config-volume naming drift (test seeds truncated name, provisioner reads full uuid) — blocks all core PRs #2499

New Issue
Closed
opened 2026-06-09 22:24:13 +00:00 by core-devops · 0 comments
core-devops commented 2026-06-09 22:24:13 +00:00
Member
Copy Link
Copy Source

core main is RED: Local Provision Lifecycle E2E (stub — REQUIRED) fails on every commit

Failing on at least the last 4 main commits (e4d82298, e9dea823, 42f77aba, 6c9cc581) and therefore failing the REQUIRED check on every open core PR (e.g. #2497, #2498 — both unrelated: one is frontend-only).

Mechanism (from run 325035 / job 435834 — not a flake)

=== Results: 5 passed, 1 failed === / FAIL: workspace STUCK in 'failed' during initial provision

The platform log shows a config-volume naming drift between the test and the provisioner:

  1. Test seeds config into ws-95f603e5-ad7-configs (13-char truncated workspace id) — PASS: seeded config.yaml into ws-95f603e5-ad7-configs.
  2. The provisioner aborts: ABORT — byok billing mode has no usable LLM credential (MISSING_BYOK_CREDENTIAL, molecule-core#1994) — the seeded credential/config is invisible to it.
  3. Auto-restart → auto-recover — no template found under workspace-configs-templates for runtime=claude-code → cannot start workspace: no config.yaml source and config volume is empty → stuck failed.
  4. Teardown removes BOTH ws-95f603e5-ad71-4fe4-954e-7802df5797c7-configs (full uuid) and ws-95f603e5-ad7-configs (truncated) — two different volumes existed.

So either configDirName (or the volume-naming convention) changed on main and tests/e2e/test_local_provision_lifecycle_e2e.sh still seeds the old name, or vice versa. Whoever changed the naming should reconcile the test + code to ONE name source (SSOT the volume-name helper into the test via a printed value, not a re-derivation).

Impact

  • Every core PR is blocked on this required check.
  • Per the no-flake SOP: this is a named mechanism, not "environmental" — re-runs won't fix it.

Evidence: run 325035 job 435834 logs (lines quoted above).

🤖 Generated with Claude Code

## core main is RED: Local Provision Lifecycle E2E (stub — REQUIRED) fails on every commit Failing on at least the last 4 main commits (e4d82298, e9dea823, 42f77aba, 6c9cc581) and therefore failing the REQUIRED check on every open core PR (e.g. #2497, #2498 — both unrelated: one is frontend-only). ## Mechanism (from run 325035 / job 435834 — not a flake) `=== Results: 5 passed, 1 failed === / FAIL: workspace STUCK in 'failed' during initial provision` The platform log shows a **config-volume naming drift between the test and the provisioner**: 1. Test seeds config into **`ws-95f603e5-ad7-configs`** (13-char truncated workspace id) — `PASS: seeded config.yaml into ws-95f603e5-ad7-configs`. 2. The provisioner aborts: `ABORT — byok billing mode has no usable LLM credential (MISSING_BYOK_CREDENTIAL, molecule-core#1994)` — the seeded credential/config is invisible to it. 3. Auto-restart → `auto-recover — no template found under workspace-configs-templates for runtime=claude-code` → `cannot start workspace: no config.yaml source and config volume is empty` → stuck `failed`. 4. Teardown removes BOTH `ws-95f603e5-ad71-4fe4-954e-7802df5797c7-configs` (full uuid) and `ws-95f603e5-ad7-configs` (truncated) — two different volumes existed. So either `configDirName` (or the volume-naming convention) changed on main and `tests/e2e/test_local_provision_lifecycle_e2e.sh` still seeds the old name, or vice versa. Whoever changed the naming should reconcile the test + code to ONE name source (SSOT the volume-name helper into the test via a printed value, not a re-derivation). ## Impact - Every core PR is blocked on this required check. - Per the no-flake SOP: this is a named mechanism, not "environmental" — re-runs won't fix it. Evidence: run 325035 job 435834 logs (lines quoted above). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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 claude-status-reaper 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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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