controller reporting runners failed to register within registration timeout window

[LePhanFF]

Hello,

I am using the recent controller v0.24.0 , and I am seeing the following. It appears the creationTimeStamp and readyTransitionTime is within 2 seconds, much less than 10 minutes. The runners are fine. But this is causing more runners to be spun up on each sync loop check. I am using GKE 1.21.11-gke.1100. The runners have no errors, except for this controller constantly reporting this info. What I eventually observe is 100+ runners over a few days. I looked at 288 issues, but there are no runners issues. I saw #300 , but this was fixed a while back. I tried v0.23.0 as well.

2022-06-07T18:03:00Z INFO actions-runner-controller.runnerreplicaset Runner failed to register itself to GitHub in timely manner. Recreating the pod to see if it resolves the issue. CAUTION: If you see this a lot, you should investigate the root cause. See https://github.com/actions-runner-controller/actions-runner-controller/issues/288{"runnerreplicaset": "self-hosted-runners/runner-deployment-svc-76bf4", "owner": "self-hosted-runners/runner-deployment-svc-76bf4-tk8rb", "creationTimestamp": "2022-06-07 14:49:37 +0000 UTC", "readyTransitionTime": "2022-06-07 14:49:39 +0000 UTC", "configuredRegistrationTimeout": "10m0s"}

[LePhanFF]

I reverted to actions-runner-controller-0.17.3 v0.22.3

The info is still shown, but now I don't see more than a few pods per hour, no run-away runner creation like with v0.24.0.

Perhaps something was introduced recently in v0.23.0 and v0.24.0