Woodpecker push-to-main pipelines fail with no steps — queue/ack errors #259

New issue

Open

opened 2026-03-31 00:58:22 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-31 00:58:22 +00:00

Contributor

Type

Bug

Lineage

Discovered during deploy validation of westside-ai-assistant PR #24. Affects multiple repos.

Repo

forgejo_admin/pal-e-platform

What Broke

Woodpecker pipelines triggered by push events to main error immediately with status "error", zero steps, and never start. PR-event pipelines work fine. Server logs show sql: no rows in result set on queue.Done: cannot ack workflow and stream: not found on done: cannot close log stream. Affects repo_ids 1, 24, 26, 29 — systemic, not repo-specific.

Repro Steps

Merge any PR to main on a Woodpecker-enabled repo
Pipeline is created with status "error"
Pipeline has steps=[], started_at=null, finished_at=null
Restart pipeline → same error immediately

Expected Behavior

Push-to-main pipelines should execute clone → test → build-and-push → update-kustomize-tag.

Environment

Cluster/namespace: woodpecker
Pod: woodpecker-server-0 (running 2d6h)
Pod: woodpecker-agent-0 (running 2d8h)
DB: woodpecker-db-1

Acceptance Criteria

Push-to-main pipelines execute steps normally
Queue ack errors resolved
No manual image builds needed for deploys

project-pal-e-platform
sop-ci-pipeline-recovery

### Type Bug ### Lineage Discovered during deploy validation of westside-ai-assistant PR #24. Affects multiple repos. ### Repo `forgejo_admin/pal-e-platform` ### What Broke Woodpecker pipelines triggered by push events to main error immediately with status "error", zero steps, and never start. PR-event pipelines work fine. Server logs show `sql: no rows in result set` on `queue.Done: cannot ack workflow` and `stream: not found` on `done: cannot close log stream`. Affects repo_ids 1, 24, 26, 29 — systemic, not repo-specific. ### Repro Steps 1. Merge any PR to main on a Woodpecker-enabled repo 2. Pipeline is created with status "error" 3. Pipeline has steps=[], started_at=null, finished_at=null 4. Restart pipeline → same error immediately ### Expected Behavior Push-to-main pipelines should execute clone → test → build-and-push → update-kustomize-tag. ### Environment - Cluster/namespace: woodpecker - Pod: woodpecker-server-0 (running 2d6h) - Pod: woodpecker-agent-0 (running 2d8h) - DB: woodpecker-db-1 ### Acceptance Criteria - [ ] Push-to-main pipelines execute steps normally - [ ] Queue ack errors resolved - [ ] No manual image builds needed for deploys ### Related - `project-pal-e-platform` - sop-ci-pipeline-recovery