Skip to content

Improve error message when job pod failed with wrong arch

People often mistakenly do use wrong arch in our pipelines or forget to put arm64 or amd64 in pipelines:

Using FF_USE_POD_ACTIVE_DEADLINE_SECONDS, the Pod activeDeadlineSeconds will be set to the job timeout: 2h0m0s...
Subscribing to Kubernetes Pod events...
Type     Reason      Message
Normal   Scheduled   Successfully assigned gitlab-runners/runner-uk35cnqgg-project-21774392-concurrent-0-6ofgefb6 to ip-10-1-10-123.ec2.internal
Normal   Pulled   Container image "registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:arm64-v18.0.2" already present on machine
Normal   Created   Created container init-permissions
Normal   Started   Started container init-permissions
Normal   Pulling   Pulling image "registry.gitlab.com/our-company/builder-java8:latest"
Normal   Pulled   Successfully pulled image "registry.gitlab.com/our-company/builder-java8:latest" in 361ms (361ms including waiting)
Normal   Created   Created container build
Normal   Started   Started container build
Normal   Pulled   Container image "registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:arm64-v18.0.2" already present on machine
Normal   Created   Created container helper
Normal   Started   Started container helper
ERROR: Job failed (system failure): prepare environment: waiting for pod running: timed out waiting for pod to start. Check https://docs.gitlab.com/runner/shells/#shell-profile-loading for more information

Can you please improve the error message to be more accurate?

It is not a timeout. To be more accurate:

Job failed (system failure): could not start job because of wrong architecture in container image

Maybe also show more messages from EventList.