-
-
Notifications
You must be signed in to change notification settings - Fork 29
Closed
Description
Upgrading from version 3.4.2 to 3.5.0. The server reports an error and fails to start.
{"level":"error","error":"can't setup globals: could not setup service manager: forge not configured","time":"2026-01-08T01:39:12Z","message":"error running server"}
my values.yaml:
agent:
replicaCount: 2
env:
WOODPECKER_BACKEND_K8S_STORAGE_RWX: false
# Agents will spawn pods to run workflow steps using the
# Kubernetes backend instead of running them directly on
# the agent pod, so we can run many workflows per agent.
WOODPECKER_MAX_WORKFLOWS: 10
mapAgentSecret: false
extraSecretNamesForEnvFrom:
- woodpecker-secret
server:
env:
WOODPECKER_HOST: https://ci.west-beta.ts.net
WOODPECKER_WEBHOOK_HOST: http://woodpecker-server.woodpecker
WOODPECKER_GITEA: true
WOODPECKER_GITEA_URL: https://git.west-beta.ts.net
WOODPECKER_OPEN: true
WOODPECKER_ADMIN: gitea_admin
ingress:
enabled: true
ingressClassName: tailscale
annotations:
tailscale.com/experimental-forward-cluster-traffic-via-ingress: "true"
hosts:
- host: &host ci.west-beta.ts.net
paths:
- path: /
tls:
- hosts:
- *host
createAgentSecret: false
extraSecretNamesForEnvFrom:
- woodpecker-secret
prometheus:
podmonitor:
enabled: true
rules:
enabled: true
grafana:
dashboards:
enabled: true
labels:
grafana_dashboard: "1"
metrics:
enabled: true
Please help. Thanks.
update: After downgrading to version 3.4.2, it returned to normal.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels