-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Finalization of pods not run when CR is deleted #212
Comments
Then there is a problem with unregistration, please provide logs from the operator to enable me to help you. |
@davidkarlsen I don't see any mention of the delete in the operator log. The delete command was issued at 12:34:23 which is the last time there is anything in the operator logs here:
|
Sorry, I just noticed I put this on the wrong project. This should probably be on the |
that's strange, what version are you running of the operator? |
I'm running the latest version from helm charts 2.5.10. I'm just testing locally in my k8s environment in docker on win10.
|
I was able to reproduce it. It's an edge case when you delete the actual cr. In this case it's gone and the cleanup step handling the finalization https://github.com/evryfs/github-actions-runner-operator/blob/master/controllers/githubactionrunner_controller.go#L116 is not reached.
|
What would be another way to tear down these resources then? |
Hi there,
I can't remove them. |
@aroemen @duyhenryer I was able to delete them by removing the finalizers field. Patch the finalizers list to be null:
|
yes, and that's what the operator does after de-registering them from github - which is why I am curious what the operator logs. |
@davidkarlsen I posted the operator logs back in March. Do you need additional data? |
Maybe the CR should have finalizer as well. |
I'm trying to make this work on latest build but cant seem to make it... I suspect that either the image i'm pulling is not the latest - or i'm pulling the image wrong, the operator image i'm pulling using the published helm charts : The runner image is this one : What am i missing ? Thx |
@tonywildey-valstro you probably don't have the lastest crd: https://raw.githubusercontent.com/evryfs/github-actions-runner-operator/v0.10.0/config/crd/bases/garo.tietoevry.com_githubactionrunners.yaml |
Ah - there we go - I installed using the helm chart: https://github.com/evryfs/helm-charts/blob/master/charts/github-actions-runner-operator/crds/garo.tietoevry.com_githubactionrunners.yaml which does not have the min runners change Thx
|
Running
kubectl apply -f .\gh-runners-linux.yaml
creates the runners as expected in my GitHub organization. When I delete them though (usingkubectl delete -f .\gh-runners-linux.yaml
), the pods that contained the runners get stuck in a "Terminating" status.If I edit the pod and remove the finalizer (garo.tietoevry.com/runner-registration), the pod successfully deletes after saving that change. The runner is not being removed from my list of GitHub self hosted runners though as I would expect. Am I missing something here?
The text was updated successfully, but these errors were encountered: