fix(e2e): clarify EIC diagnose SG guidance #1664

Merged
hongming merged 1 commits from fix/e2e-eic-diagnostic-sg into main 2026-05-22 02:47:29 +00:00
Owner

What

  • Remove the deleted hard-coded EIC endpoint SG from the staging E2E terminal diagnose failure message.
  • Point operators at the canonical Railway env MOLECULE_EIC_ENDPOINT_SG_ID.

Why

The live staging EIC endpoint SG is resolved from AWS/Railway config. A stale hard-coded SG in the failure text sent investigation toward a deleted security group even after CP was correctly wiring the live endpoint SG.

SOP

  • Comprehensive testing performed: bash syntax, shellcheck, diff check, and live staging EIC probe.
  • Local-postgres E2E run: N/A, E2E shell diagnostic text only; no Postgres behavior changed.
  • Staging-smoke verified or pending: manual staging smoke reached terminal-reachable and Files API EIC write HTTP 200 after Railway env fix; later A2A 503 was expected because the manual probe intentionally omitted LLM credentials.
  • Root-cause not symptom: Railway staging had only the legacy EIC_ENDPOINT_SG_ID name while CP uses canonical MOLECULE_EIC_ENDPOINT_SG_ID; the repo diagnostic also hard-coded a deleted SG.
  • Five-Axis review walked: correctness/readability/architecture/security/performance checked; change is diagnostic text only.
  • No backwards-compat shim / dead code added: no shim, no runtime behavior change.
  • Memory/saved-feedback consulted: Gitea status enum and SOP/review gate patterns from saved guidance were applied.

Verification

  • bash -n tests/e2e/test_staging_full_saas.sh
  • shellcheck -x tests/e2e/test_staging_full_saas.sh
  • git diff --check
  • Manual staging smoke reached terminal-reachable and Files API EIC write HTTP 200; teardown verified no EC2 leak.
## What - Remove the deleted hard-coded EIC endpoint SG from the staging E2E terminal diagnose failure message. - Point operators at the canonical Railway env `MOLECULE_EIC_ENDPOINT_SG_ID`. ## Why The live staging EIC endpoint SG is resolved from AWS/Railway config. A stale hard-coded SG in the failure text sent investigation toward a deleted security group even after CP was correctly wiring the live endpoint SG. ## SOP - [x] Comprehensive testing performed: bash syntax, shellcheck, diff check, and live staging EIC probe. - [x] Local-postgres E2E run: N/A, E2E shell diagnostic text only; no Postgres behavior changed. - [x] Staging-smoke verified or pending: manual staging smoke reached `terminal-reachable` and Files API EIC write HTTP 200 after Railway env fix; later A2A 503 was expected because the manual probe intentionally omitted LLM credentials. - [x] Root-cause not symptom: Railway staging had only the legacy `EIC_ENDPOINT_SG_ID` name while CP uses canonical `MOLECULE_EIC_ENDPOINT_SG_ID`; the repo diagnostic also hard-coded a deleted SG. - [x] Five-Axis review walked: correctness/readability/architecture/security/performance checked; change is diagnostic text only. - [x] No backwards-compat shim / dead code added: no shim, no runtime behavior change. - [x] Memory/saved-feedback consulted: Gitea status enum and SOP/review gate patterns from saved guidance were applied. ## Verification - `bash -n tests/e2e/test_staging_full_saas.sh` - `shellcheck -x tests/e2e/test_staging_full_saas.sh` - `git diff --check` - Manual staging smoke reached `terminal-reachable` and Files API EIC write HTTP 200; teardown verified no EC2 leak.
hongming added 1 commit 2026-05-22 02:38:46 +00:00
Clarify EIC diagnose SG guidance
Lint shellcheck (arm64 pilot) / shellcheck-arm64 (pilot) (pull_request) Waiting to run
Block internal-flavored paths / Block forbidden paths (pull_request) Successful in 3s
CI / Python Lint & Test (pull_request) Successful in 6s
CI / Detect changes (pull_request) Successful in 7s
E2E API Smoke Test / detect-changes (pull_request) Successful in 7s
E2E Staging SaaS (full lifecycle) / E2E Staging SaaS (pull_request) Has been skipped
E2E Chat / detect-changes (pull_request) Successful in 7s
E2E Staging Canvas (Playwright) / detect-changes (pull_request) Successful in 7s
Handlers Postgres Integration / detect-changes (pull_request) Successful in 5s
Lint forbidden tenant-env keys / Scan workspace_secrets writers for forbidden env keys (pull_request) Successful in 7s
Lint no tenant GITEA or GITHUB token write / Scan for repo-host token write into tenant workspace surface (pull_request) Successful in 5s
Secret scan / Scan diff for credential-shaped strings (pull_request) Successful in 7s
CI / Platform (Go) (pull_request) Successful in 2s
CI / Canvas (Next.js) (pull_request) Successful in 2s
E2E Chat / E2E Chat (pull_request) Successful in 6s
CI / Shellcheck (E2E scripts) (pull_request) Successful in 9s
E2E Staging SaaS (full lifecycle) / pr-validate (pull_request) Successful in 34s
CI / Canvas Deploy Reminder (pull_request) Has been skipped
Handlers Postgres Integration / Handlers Postgres Integration (pull_request) Successful in 3s
E2E Staging Canvas (Playwright) / Canvas tabs E2E (pull_request) Successful in 4s
CI / all-required (pull_request) Successful in 51s
lint-required-no-paths / lint-required-no-paths (pull_request) Successful in 1m8s
E2E API Smoke Test / E2E API Smoke Test (pull_request) Successful in 1m2s
qa-review / approved (pull_request) Refired via /qa-recheck by unknown
security-review / approved (pull_request) Refired via /security-recheck by unknown
sop-checklist / review-refire (pull_request) Has been skipped
gate-check-v3 / gate-check (pull_request) Successful in 4s
sop-tier-check / tier-check (pull_request) Successful in 4s
sop-checklist / all-items-acked (pull_request) acked: 7/7
sop-checklist / na-declarations (pull_request) N/A: (none)
audit-force-merge / audit (pull_request) Successful in 6s
086b479dca
core-qa approved these changes 2026-05-22 02:44:32 +00:00
core-qa left a comment
Member

Approved for CI/E2E diagnostic cleanup. Scope is a stale failure message only; live EIC path was verified separately.

Approved for CI/E2E diagnostic cleanup. Scope is a stale failure message only; live EIC path was verified separately.
core-security approved these changes 2026-05-22 02:44:33 +00:00
core-security left a comment
Member

Approved for CI/E2E diagnostic cleanup. Scope is a stale failure message only; live EIC path was verified separately.

Approved for CI/E2E diagnostic cleanup. Scope is a stale failure message only; live EIC path was verified separately.
Author
Owner

/sop-ack 1 2 3 4 5 6 7

/sop-ack 1 2 3 4 5 6 7
Member

/sop-ack comprehensive-testing local-postgres-e2e staging-smoke root-cause five-axis-review no-backwards-compat memory-consulted

/sop-ack comprehensive-testing local-postgres-e2e staging-smoke root-cause five-axis-review no-backwards-compat memory-consulted
Member

/sop-ack comprehensive-testing local-postgres-e2e staging-smoke root-cause five-axis-review no-backwards-compat memory-consulted

/sop-ack comprehensive-testing local-postgres-e2e staging-smoke root-cause five-axis-review no-backwards-compat memory-consulted
Member

/sop-ack local-postgres-e2e staging-smoke root-cause five-axis-review no-backwards-compat memory-consulted

/sop-ack local-postgres-e2e staging-smoke root-cause five-axis-review no-backwards-compat memory-consulted
Member

/sop-ack 3 4 5 6 7

/sop-ack 3 4 5 6 7
Member

/sop-ack 4

/sop-ack 4
Member

/sop-ack 5

/sop-ack 5
Member

/sop-ack 6

/sop-ack 6
Member

/sop-ack 7

/sop-ack 7
hongming merged commit 992ccfbd5e into main 2026-05-22 02:47:29 +00:00
hongming deleted branch fix/e2e-eic-diagnostic-sg 2026-05-22 02:47:29 +00:00
Sign in to join this conversation.
4 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#1664