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

[harness][tracking] canary-smoke-org-create-400-capture xfail: cp-stub lacks /cp/admin/orgs route (404) + 400 body empty under set -e + admin_call #2864

New Issue
Closed
opened 2026-06-14 16:37:21 +00:00 by agent-dev-b · 0 comments
agent-dev-b commented 2026-06-14 16:37:21 +00:00
Member
Copy Link
Copy Source

Tracking issue for xfail on #2821

Failure (run #365912 on head 2e485167, replay #365912.5) — the actual core#2737 staging SaaS smoke

canary-smoke-org-create-400-capture:

✗ expected 400, got 404 (cp-stub may have a different validation shape — see body above)
✗ 400 response body is EMPTY — this is the staging script's failure (loses the actionable reason under set -e + admin_call)
[replay] PASS=1 FAIL=2

Why this matters

This is the actual core#2737 staging SaaS smoke that PR #2821 was meant to capture! The replay now reproduces the staging 400-body-loss locally (which is the win — the test capture works). But the underlying issue is the cp-stub lacks the /cp/admin/orgs route that the production CP has.

Two-part failure

  1. 404 instead of 400: harness cp-stub only registers /cp/admin/tenants/redeploy-fleet (per tests/harness/cp-stub/main.go:53). The replay posts to /cp/admin/orgs and gets 404. Production CP returns 400 (validation error) for a malformed org-create payload.
  2. Empty 400 body: even when production returns 400, the body is empty under the staging script's set -e + admin_call combo — this is the actionable reason that the human approver loses. Need to fix the script-side error handling (or CP-side body) to surface the validation reason.

Why xfail, not fix-in-PR

Two separate fixes (cp-stub route + body-capture handling) that are out of scope for #2821 (which is the test capture PR). Tracking the work here.

Acceptance criteria for un-xfail

  1. tests/harness/cp-stub/main.go registers a /cp/admin/orgs route that returns 400 + JSON body with {error, validation_reasons} for a malformed org-create payload.
  2. The replay's set -e + admin_call surfaces the body in stderr on non-2xx responses.
  3. canary-smoke-org-create-400-capture.sh runs end-to-end with PASS=3 FAIL=0 (or PASS=2 FAIL=0 if the 400-body-capture sub-assertion is split out as a separate xfail).
  4. Harness Replays on the rebased head is fully green without xfail.
## Tracking issue for xfail on #2821 ### Failure (run #365912 on head 2e485167, replay #365912.5) — the actual core#2737 staging SaaS smoke `canary-smoke-org-create-400-capture`: ``` ✗ expected 400, got 404 (cp-stub may have a different validation shape — see body above) ✗ 400 response body is EMPTY — this is the staging script's failure (loses the actionable reason under set -e + admin_call) [replay] PASS=1 FAIL=2 ``` ### Why this matters This is the **actual core#2737 staging SaaS smoke** that PR #2821 was meant to capture! The replay now reproduces the staging 400-body-loss locally (which is the win — the test capture works). But the underlying issue is the cp-stub lacks the `/cp/admin/orgs` route that the production CP has. ### Two-part failure 1. **404 instead of 400**: harness cp-stub only registers `/cp/admin/tenants/redeploy-fleet` (per `tests/harness/cp-stub/main.go:53`). The replay posts to `/cp/admin/orgs` and gets 404. Production CP returns 400 (validation error) for a malformed org-create payload. 2. **Empty 400 body**: even when production returns 400, the body is empty under the staging script's `set -e + admin_call` combo — this is the actionable reason that the human approver loses. Need to fix the script-side error handling (or CP-side body) to surface the validation reason. ### Why xfail, not fix-in-PR Two separate fixes (cp-stub route + body-capture handling) that are out of scope for #2821 (which is the test capture PR). Tracking the work here. ### Acceptance criteria for un-xfail 1. `tests/harness/cp-stub/main.go` registers a `/cp/admin/orgs` route that returns 400 + JSON body with `{error, validation_reasons}` for a malformed org-create payload. 2. The replay's set -e + admin_call surfaces the body in stderr on non-2xx responses. 3. `canary-smoke-org-create-400-capture.sh` runs end-to-end with PASS=3 FAIL=0 (or PASS=2 FAIL=0 if the 400-body-capture sub-assertion is split out as a separate xfail). 4. Harness Replays on the rebased head is fully green without xfail.
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#2864
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?