molecule-ai/molecule-core
53
0
Fork 2
Code Issues 187 Pull Requests 45 Actions 4 Packages Projects Releases Wiki Activity

Concierge boot-install can't authenticate the gitea plugin fetch (404) — no GIT_HTTP creds; needs MOLECULE_TEMPLATE_REPO_TOKEN auth [next layer after #872] #3065

New Issue
Closed
opened 2026-06-19 05:35:19 +00:00 by molecule-code-reviewer · 0 comments
molecule-code-reviewer commented 2026-06-19 05:35:19 +00:00
Member
Copy Link
Copy Source

Gap (next layer after #872): concierge boot-install can't AUTH the gitea plugin fetch → 404 → no create_workspace

After CP #872 (RFC #3045, retire the special image) the concierge now runs the standard claude-code image and its plugin boot-install runs — verified live on a fresh staging concierge (box image = workspace-template-claude-code). But the plugin fetch fails:

curl: (22) The requested URL returned error: 404
[plugins] fetch/extract failed: gitea://molecule-ai/molecule-ai-plugin-molecule-platform-mcp#main
::warning::GIT_HTTP_USERNAME or GIT_HTTP_PASSWORD not set; skipping ~/.netrc setup. Gitea curl calls will need an alternative safe-auth method.

Root cause (isolated)

  • The repo + ref + URL are correct: GET /api/v1/repos/molecule-ai/molecule-ai-plugin-molecule-platform-mcp/archive/main.tar.gz returns HTTP 200 with a valid token (private repo, main, non-empty).
  • The box's boot-install gitea curl is unauthenticated: scripts/setup-gitea-netrc.sh (runtime image) needs GIT_HTTP_USERNAME/GIT_HTTP_PASSWORD, injected by core applyAgentGitHTTPCreds from /etc/molecule-bootstrap/personas/<role>/token. The concierge has no persona token file (it's not a fleet persona) → no GIT_HTTP creds → netrc skipped → unauthenticated curl → 404 on the private plugin repo.
  • The box DOES hold MOLECULE_TEMPLATE_REPO_TOKEN (the read-only template/plugin fetch token) — but the shell boot-install doesn't use it for auth. (The Go gitea resolver plugins/gitea.go DOES use that token, but the on-box boot-install is a separate shell path that relies on netrc.)
  • seo-all installs because seo-agent boxes get persona GIT_HTTP creds (or the seo-agent template repo is reached differently); the concierge gets neither.

Fix (pick one)

  • (core, smallest) For the concierge, set GIT_HTTP_USERNAME + GIT_HTTP_PASSWORD from MOLECULE_TEMPLATE_REPO_TOKEN in the concierge provision env (e.g. conciergePlatformMCPEnv / applyConciergeProvisionConfig) so setup-gitea-netrc.sh authenticates the plugin fetch. The token is read-only (safe; survives the SCM-write denylist via the GIT_HTTP_* names).
  • (runtime image, most general) setup-gitea-netrc.sh falls back to MOLECULE_TEMPLATE_REPO_TOKEN (as password, with a fixed username) when GIT_HTTP_* / GITEA_* are absent — fixes plugin-fetch auth for ANY plugin-using workspace, not just the concierge.

Chain status (concierge → create_workspace)

ECR cross-account (infra, fixed) → declares gitea:// plugin (#3049, merged) → restart no longer re-stubs (#3055, merged) → runs plugin-capable claude-code image (#872, merged+verified) → THIS: boot-install auths the gitea plugin fetch → plugin installs → MCPServerAdaptor wires mcpServers.molecule-platform → create_workspace. This is the next (and hopefully last-but-one) link; Task #52 still open.

Refs RFC #3045, #872, core#3063, #3049.

## Gap (next layer after #872): concierge boot-install can't AUTH the gitea plugin fetch → 404 → no create_workspace After CP #872 (RFC #3045, retire the special image) the concierge now runs the **standard claude-code image** and its plugin boot-install **runs** — verified live on a fresh staging concierge (box image = `workspace-template-claude-code`). But the plugin fetch fails: ``` curl: (22) The requested URL returned error: 404 [plugins] fetch/extract failed: gitea://molecule-ai/molecule-ai-plugin-molecule-platform-mcp#main ::warning::GIT_HTTP_USERNAME or GIT_HTTP_PASSWORD not set; skipping ~/.netrc setup. Gitea curl calls will need an alternative safe-auth method. ``` ## Root cause (isolated) - The repo + ref + URL are correct: `GET /api/v1/repos/molecule-ai/molecule-ai-plugin-molecule-platform-mcp/archive/main.tar.gz` returns **HTTP 200 with a valid token** (private repo, main, non-empty). - The box's boot-install gitea curl is **unauthenticated**: `scripts/setup-gitea-netrc.sh` (runtime image) needs `GIT_HTTP_USERNAME`/`GIT_HTTP_PASSWORD`, injected by core `applyAgentGitHTTPCreds` from `/etc/molecule-bootstrap/personas/<role>/token`. The **concierge has no persona token file** (it's not a fleet persona) → no GIT_HTTP creds → netrc skipped → unauthenticated curl → **404** on the private plugin repo. - The box DOES hold `MOLECULE_TEMPLATE_REPO_TOKEN` (the read-only template/plugin fetch token) — but the shell boot-install doesn't use it for auth. (The Go gitea resolver `plugins/gitea.go` DOES use that token, but the on-box boot-install is a separate shell path that relies on netrc.) - `seo-all` installs because seo-agent boxes get persona GIT_HTTP creds (or the seo-agent template repo is reached differently); the concierge gets neither. ## Fix (pick one) - **(core, smallest)** For the concierge, set `GIT_HTTP_USERNAME` + `GIT_HTTP_PASSWORD` from `MOLECULE_TEMPLATE_REPO_TOKEN` in the concierge provision env (e.g. `conciergePlatformMCPEnv` / `applyConciergeProvisionConfig`) so `setup-gitea-netrc.sh` authenticates the plugin fetch. The token is read-only (safe; survives the SCM-write denylist via the GIT_HTTP_* names). - **(runtime image, most general)** `setup-gitea-netrc.sh` falls back to `MOLECULE_TEMPLATE_REPO_TOKEN` (as password, with a fixed username) when `GIT_HTTP_*` / `GITEA_*` are absent — fixes plugin-fetch auth for ANY plugin-using workspace, not just the concierge. ## Chain status (concierge → create_workspace) ECR cross-account (infra, fixed) → declares gitea:// plugin (#3049, merged) → restart no longer re-stubs (#3055, merged) → runs plugin-capable claude-code image (#872, merged+verified) → **THIS: boot-install auths the gitea plugin fetch** → plugin installs → MCPServerAdaptor wires `mcpServers.molecule-platform` → `create_workspace`. This is the next (and hopefully last-but-one) link; Task #52 still open. Refs RFC #3045, #872, core#3063, #3049.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 platform/go
Go platform test issues
 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#3065
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?