forgejo_admin/pal-e-docs-app
1
0
Fork 0
Code Issues 4 Pull requests 1 Projects Releases Packages Wiki Activity Actions

fix: replace plugin-git clone with alpine/git + sleep to fix CI clone failure #92

New issue
Closed
opened 2026-03-28 20:12:10 +00:00 by forgejo_admin · 0 comments
forgejo_admin commented 2026-03-28 20:12:10 +00:00
Owner
Copy link

Type

Bug

Lineage

Related to forgejo_admin/pal-e-platform #234 — pal-e-docs-app pod ImagePullBackOff investigation.

Repo

forgejo_admin/pal-e-docs-app

What Broke

All CI pipelines fail at the clone step with:

fatal: unable to access 'http://forgejo-http.forgejo.svc.cluster.local/.../pal-e-docs-app.git/':
Failed to connect to forgejo-http.forgejo.svc.cluster.local port 80 after 2 ms: Could not connect to server

No image has ever been pushed to the pal-e-docs-app Harbor project, causing ImagePullBackOff in the pal-e-docs-app namespace.

Repro Steps

  1. Push any commit to pal-e-docs-app main branch
  2. Woodpecker triggers pipeline
  3. Clone step fails immediately with connection refused
  4. All downstream steps (test, build, push) never run

Expected Behavior

Clone step connects to Forgejo internal service and fetches the repo, matching the behavior of all other repos (basketball-api, pal-e-docs, etc.).

Environment

  • Cluster/namespace: prod / woodpecker (pipeline pods)
  • Service version/commit: Woodpecker v3.13.0, pipeline #108
  • Related alerts: pal-e-docs-app pod ImagePullBackOff

Acceptance Criteria

  • CI clone step succeeds
  • Pipeline reaches build-and-push step
  • Image pushed to Harbor pal-e-docs-app/app project

Related

  • forgejo_admin/pal-e-platform #234 — parent tracking issue
### Type Bug ### Lineage Related to `forgejo_admin/pal-e-platform #234` — pal-e-docs-app pod ImagePullBackOff investigation. ### Repo `forgejo_admin/pal-e-docs-app` ### What Broke All CI pipelines fail at the clone step with: ``` fatal: unable to access 'http://forgejo-http.forgejo.svc.cluster.local/.../pal-e-docs-app.git/': Failed to connect to forgejo-http.forgejo.svc.cluster.local port 80 after 2 ms: Could not connect to server ``` No image has ever been pushed to the `pal-e-docs-app` Harbor project, causing ImagePullBackOff in the pal-e-docs-app namespace. ### Repro Steps 1. Push any commit to pal-e-docs-app main branch 2. Woodpecker triggers pipeline 3. Clone step fails immediately with connection refused 4. All downstream steps (test, build, push) never run ### Expected Behavior Clone step connects to Forgejo internal service and fetches the repo, matching the behavior of all other repos (basketball-api, pal-e-docs, etc.). ### Environment - Cluster/namespace: prod / woodpecker (pipeline pods) - Service version/commit: Woodpecker v3.13.0, pipeline #108 - Related alerts: pal-e-docs-app pod ImagePullBackOff ### Acceptance Criteria - [ ] CI clone step succeeds - [ ] Pipeline reaches build-and-push step - [ ] Image pushed to Harbor `pal-e-docs-app/app` project ### Related - `forgejo_admin/pal-e-platform #234` — parent tracking issue
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
226-fix-wget-auth
No results found.
Labels
Clear labels   
domain:backend

   
domain:devops

   
domain:frontend
No labels
domain:backend
domain:devops
domain:frontend
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo_admin/pal-e-docs-app#92
No description provided.