wpp/weirsoe-party-protocol
8
0
Fork 0
Code Issues 19 Pull Requests Actions Packages Projects Releases Wiki Activity

[devops][need-to-have] deploy_staging.sh health check race blocks release-readiness #141

New Issue
Closed
opened 2026-02-28 18:35:32 +01:00 by dev-bot · 1 comment
dev-bot commented 2026-02-28 18:35:32 +01:00
Owner
Copy Link

Problem
infra/staging/deploy_staging.sh fejler periodisk i canonical flow med curl: (7) Failed to connect to 127.0.0.1:8000 lige efter restart, selv når service kort efter er active og /healthz svarer OK.

Forventet værdi

  • Stabil, reproducerbar release-readiness verifikation uden falske FAIL.
  • Mindre manuel driftstøj og færre no-op reruns i release-sporet.

Hvorfor nu
Release-readiness issue #90 er fortsat blokeret specifikt af dette punkt, selv efter at staging smoke passerer.

Acceptkriterier

  • deploy_staging.sh bruger bounded retry/backoff for post-restart health check (ikke uendelig vent).
  • Script returnerer 0 når service bliver sund inden for retry-vinduet.
  • Script returnerer non-zero med tydelig fejl hvis service ikke bliver sund inden for vinduet.
  • Verificeret i staging med samme canonical flow som i #90.

Artifacts ved completion

  • Commit SHA + PR link
  • Kort verifikationslog (deploy + health + smoke)
Problem `infra/staging/deploy_staging.sh` fejler periodisk i canonical flow med `curl: (7) Failed to connect to 127.0.0.1:8000` lige efter restart, selv når service kort efter er `active` og `/healthz` svarer OK. Forventet værdi - Stabil, reproducerbar release-readiness verifikation uden falske FAIL. - Mindre manuel driftstøj og færre no-op reruns i release-sporet. Hvorfor nu Release-readiness issue #90 er fortsat blokeret specifikt af dette punkt, selv efter at staging smoke passerer. Acceptkriterier - `deploy_staging.sh` bruger bounded retry/backoff for post-restart health check (ikke uendelig vent). - Script returnerer 0 når service bliver sund inden for retry-vinduet. - Script returnerer non-zero med tydelig fejl hvis service ikke bliver sund inden for vinduet. - Verificeret i staging med samme canonical flow som i #90. Artifacts ved completion - Commit SHA + PR link - Kort verifikationslog (deploy + health + smoke)
dev-bot added the bot-taskneed-to-havedevopsstaging labels 2026-02-28 18:35:32 +01:00
dev-bot commented 2026-02-28 18:37:21 +01:00
Author
Owner
Copy Link

Scheduler artifact update: Dev-fix leveret i PR #142 (fix/141-staging-healthcheck-retry) med head/commit SHA c4ea5ca20853b2ee6752013881578e03abfb3970. Scope matcher #141 (bounded retry/backoff + tydelig non-zero diagnostics). Næste: review + staging verify via canonical deploy-flow.

Scheduler artifact update: Dev-fix leveret i PR #142 (`fix/141-staging-healthcheck-retry`) med head/commit SHA `c4ea5ca20853b2ee6752013881578e03abfb3970`. Scope matcher #141 (bounded retry/backoff + tydelig non-zero diagnostics). Næste: review + staging verify via canonical deploy-flow.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
PO vil have det her prioriteret
PO-prioriteret
 architect
Architect-owned coordination thread
 backend
Backend
 bot-task
Task managed by scheduler bots
 devops
DevOps/deploy related
 epic
Long-lived scope/phase tracking
 frontend
Frontend
 i18n
Internationalization
 mvp
auto by architect runner
 need-to-have
Required before merge/release
 needs-approval
Requires PO approval before execution
 nice-to-have
Improvement not blocking MVP
 release-approved
Architect approved release scope
 resolved
Løst og merged
 scope-guardrail
Scope and acceptance criteria source-of-truth
 smoke-fail
Smoke test failure
 spa
auto by architect runner
 staging
Staging infrastructure/deploy
 stale
Ingen aktivitet / forældet ift. main
 ui
Frontend/UI related
No Label bot-task devops need-to-have staging
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
architecture-bot dev-bot email-manager integrator-bot manager-bot reviewer-bot scheduler-bot tester-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#141
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?