Custom runner that is online, and gets a job assigned, but doesn't start any jobs

[lazee]

Hi,

This might be an issues that has been discussed already, but I was not able to find any. I have installed a custom runner, in our Kubernetes, for handling automatic dependency submission. On organization level in Github.

The reason for not using a default Github runner, is that our Maven pom files contains private packages, that Github cannot reach. The Runner seems to register itself correctly and reports that it is online

When Github run the dependency job, I get this in the job log:

In the runner I get these logs:

{"severity":"info","ts":"2024-12-11T11:03:04Z","logger":"listener-app.listener","message":"New runner scale set statistics.","statistics":{"totalAvailableJobs":0,"totalAcquiredJobs":0,"totalAssignedJobs":1,"totalRunningJobs":0,"totalRegisteredRunners":0,"totalBusyRunners":0,"totalIdleRunners":0}}
{"severity":"info","ts":"2024-12-11T11:03:04Z","logger":"listener-app.listener","message":"Job assigned message received","jobId":594947}
{"severity":"info","ts":"2024-12-11T11:03:04Z","logger":"listener-app.listener","message":"Deleting last message","lastMessageID":7}
{"severity":"info","ts":"2024-12-11T11:03:05Z","logger":"listener-app.worker.kubernetesworker","message":"Created merge patch json for EphemeralRunnerSet update","json":"{\"spec\":{\"replicas\":2}}"}
{"severity":"info","ts":"2024-12-11T11:03:05Z","logger":"listener-app.worker.kubernetesworker","message":"Scaling ephemeral runner set","assigned job":1,"decision":2,"min":1,"max":2147483647,"currentRunnerCount":-1}
{"severity":"info","ts":"2024-12-11T11:03:05Z","logger":"listener-app.worker.kubernetesworker","message":"Ephemeral runner set scaled.","namespace":"actions-runner-system","name":"dependency-submission-j49m4","replicas":2}
{"severity":"info","ts":"2024-12-11T11:03:05Z","logger":"listener-app.listener","message":"Getting next message","lastMessageID":7}

So, it seems like the job is assigned, but never executed.

Anybody else that have had a similar problem? Any help would be much appreciated.

[lazee]

I turned out I had errors in our Helm config, and no runners were actually started.