-
-
Notifications
You must be signed in to change notification settings - Fork 358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pipeline with service doesn't work (K8s) #3178
Comments
Hi, I am not able to use rwx volumes in my clusters, when I try with NFS services, the pipelines go to very slow to finish. In my situation, the services start-up with a volume and lock it. It is blocking the other pod steps to continue. My suggestion is to create the pod service with an empty dir, without the volume used in the other pods steps. It's make the pods services isolated from the pv mount lock |
I don't think, that volume is the cause of this issue. On Perhaps, #3141 is related. |
Thanks, I'm running 2.1.1. I will try replicate my issue with
|
It was broken twice: in #3141 and #3135. 1-woodpecker-agent-549d095f.log works. 6-woodpecker-agent-d1fe86b7-patched.log broken again. The same on skip_clone: true
services:
server:
image: digitalocean/doks-debug
commands:
- echo 'This is test server' | nc -l -6 1234
ports:
- 1234
steps:
client:
image: digitalocean/doks-debug
commands:
- nc -v -6 -w 10 server 1234
Pipeline 120 skip_clone: true
services:
server:
image: alpine
commands:
- echo Hello from service
ports:
- 1234
steps:
client:
image: alpine
commands:
- echo Hello from step |
to not break it again - can we mock the kubernetis api somehow and create a integration test for the backend (with a smal pipeline as run example (1x clone 1x service 3xstep (2xparalel and one waiting))? |
Component
server, agent
Describe the bug
When running pipeline with service, it going to start, but there is no pods and even attempts to create them.
There are no errors and WP pods (Server, Agent) restarts.
Pipeline:
Result:
System Info
`next-a5fa810bcc`
Additional context
woodpecker-server.log
woodpecker-agent.log
https://woodpecker.test.smthd.com/repos/1/pipeline/85
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: