The ARC 0.8.3 giving issue on creating listener and "error": "EphemeralRunnerSet.actions.github.com \"eks-mcdevops-runner-j4flc\" is invalid: spec.patchID: Required value"

[aakashvishwakarma]

Hi team, I m deploying and testing ARC with version 0.8.3 , i find it out that controller got created but when deploying the runnerset neither listener nor runner pod coming up on checking controller logs i find it out that:
Below error it is throwing
2024-03-28T16:59:56Z ERROR Reconciler error {"controller": "autoscalingrunnerset", "controllerGroup": "actions.github.com", "controllerKind": "AutoscalingRunnerSet", "AutoscalingRunnerSet": {"name":"eks-mcdevops-runner","namespace":"arc-runner"}, "namespace": "arc-runner", "name": "eks-mcdevops-runner", "reconcileID": "c9108a7f-b3e2-4282-9e2c-7d284b002e0f", "error": "EphemeralRunnerSet.actions.github.com \"eks-mcdevops-runner-j4flc\" is invalid: spec.patchID: Required value"}

On checking the CRDs and go code i get to know that patchID is provided by listener only. So my question is why this behavior all of a sudden in github provided ARC 0.8.3 .

Looking forward to hear back
Thank You
Aakash Vishwakarma

[aakashvishwakarma]

Hi @nikola-jokic may i know if you can help me out debugging the issue and what is the root cause as we are working for enterprise level customer in prod.

Thank you

[dcardellino24]

We managed to fix this error by manually editing the ephemeralrunnerset and add a random integer to spec.patchID. Then again edit the resource and removed the finalizer.
Afterwards new resources were created. But thats kinda hacky workaround. Better it should not happen :)

[rekha-prakash-maersk]

@dcardellino24 I am running into the same issue while upgrading from 0.8.3 to 0.9.0. Can you please explain how you have added the spec.patchID manually ? I just have the controller running in 0.9.0 version with this error and no listener getting created

[nocturne1]

This method allowed me to remove the old ephemeralrunnerset:
#3395 (comment)

[rekha-prakash-maersk]

Hi @nocturne1 , Thank you!! I was able to resolve the issue related to spec.patchID. Now the controller still wants to connect to old listener. How can I delete those old scaleset references in the controller , so it will create new listeners from the config ?

[aakashvishwakarma]

@dcardellino24 i get it manually updating is fine but i wanted to know the reason why it happened and is there any chance it can happen in other new version upgrades?
I m documenting this as we are setting up EKS runners for an Enterprise customers.

[cheskayang]

running into the same issue when reverting from 0.9.1 to 0.8.3 due to another error #3499