You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our cluster, the agent controller will keep reattempting a number of jobs despite these jobs either being failed or cancelled within the UI. It will recreate these pods over and over again no matter how many times I manually clean them up. When I grab the logs from the agent container I see that the agent container properly exits. However, when I grab the logs from container-0, I see that the buildkite agent has seg faulted and the container never exists. Every single one of these pipelines had eventually failed for one reason or another on the original run.
Agent Container Logs
2024-12-28 21:52:34 NOTICE Starting buildkite-agent v3.87.0 with PID: 8
2024-12-28 21:52:34 NOTICE The agent source code can be found here: https://github.com/buildkite/agent
2024-12-28 21:52:34 NOTICE For questions and support, email us at: [email protected]
2024-12-28 21:52:34 INFO Configuration loaded path=/home/agent/buildkite/config
2024-12-28 21:52:34 INFO Build Path doesn't exist, creating it (/workspace/build)
2024-12-28 21:52:34 INFO Registering agent with Buildkite...
2024-12-28 21:52:34 INFO Successfully registered agent "buildkite-01940a29-f1c4-44bf-88d2-672719abb132-9f4f2" with tags [k8s:agent-stack-version=v0.20.1, k8s:service-account=buildkite-build-agent, k8s:namespace=jenkins, k8s:node=ip-10-16-70-42.us-west-2.compute.internal, queue=default-queue]
2024-12-28 21:52:34 INFO Starting 1 Agent(s)
2024-12-28 21:52:34 INFO You can press Ctrl-C to stop the agents
2024-12-28 21:52:34 INFO buildkite-01940a29-f1c4-44bf-88d2-672719abb132-9f4f2 Connecting to Buildkite...
2024-12-28 21:52:34 INFO buildkite-01940a29-f1c4-44bf-88d2-672719abb132-9f4f2 Attempting to acquire job 01940a29-f1c4-44bf-88d2-672719abb132...
2024-12-28 21:52:34 WARN buildkite-01940a29-f1c4-44bf-88d2-672719abb132-9f4f2 Buildkite rejected the call to acquire the job (PUT https://agent.buildkite.com/v3/jobs/01940a29-f1c4-44bf-88d2-672719abb132/acquire: 422 Unprocessable Entity: Cannot acquire job 01940a29-f1c4-44bf-88d2-672719abb132 as it's been assigned to agent 01940a2a-0455-4b09-8f2c-cf413549dc3d)
2024-12-28 21:52:34 INFO buildkite-01940a29-f1c4-44bf-88d2-672719abb132-9f4f2 Disconnecting...
2024-12-28 21:52:34 INFO buildkite-01940a29-f1c4-44bf-88d2-672719abb132-9f4f2 Disconnected
failed to acquire job: job acquisition rejected: PUT https://agent.buildkite.com/v3/jobs/01940a29-f1c4-44bf-88d2-672719abb132/acquire: 422 Unprocessable Entity: Cannot acquire job 01940a29-f1c4-44bf-88d2-672719abb132 as it's been assigned to agent 01940a2a-0455-4b09-8f2c-cf413549dc3d
In our cluster, the agent controller will keep reattempting a number of jobs despite these jobs either being failed or cancelled within the UI. It will recreate these pods over and over again no matter how many times I manually clean them up. When I grab the logs from the agent container I see that the agent container properly exits. However, when I grab the logs from container-0, I see that the buildkite agent has seg faulted and the container never exists. Every single one of these pipelines had eventually failed for one reason or another on the original run.
Agent Container Logs
container-0 logs
The text was updated successfully, but these errors were encountered: