Closed Gabryel8818 closed 1 year ago
Hello! Thank you for filing an issue.
The maintainers will triage your issue shortly.
In the meantime, please take a look at the troubleshooting guide for bug reports.
If this is a feature request, please review our contribution guidelines.
I managed to find the error, the github_app_id and github_app_installation_id were reversed, unfortunately this is not coming out in the logs clearly, only when we create an HRA
I managed to find the error, the github_app_id and github_app_installation_id were reversed, unfortunately this is not coming out in the logs clearly, only when we create an HRA
Hey Gabryel! How to you fixed it? could you share the solution? I have the same issue.
Hi! Is there any solution available for this? I'm facing the same log entry and runners are not getting scheduled. Could this be issue with Github API? Limit etc?
Checks
Controller Version
0.27.0
Helm Chart Version
0.22.0
CertManager Version
1.11.0
Deployment Method
Helm
cert-manager installation
i follow: https://cert-manager.io/docs/installation/helm/
helm install \ cert-manager jetstack/cert-manager \ --namespace cert-manager \ --create-namespace \ --version v1.11.0 \ --set installCRDs=true
Checks
Resource Definitions
To Reproduce
Describe the bug
When using the github app secrets the controller goes up normally, but when trying to start a corridor we have the following log:
manager {"severity":"debug","ts":1679582076.8447473,"logger":"runnerreplicaset","message":"Skipped reconcilation because owner is not synced yet","runnerreplicaset":"github-self-hosted/example-runnerdeploy-9qnzv","owner":"github-self-hosted/example-runnerdeploy-9qnzv-s46r8","pods":null}
when using Github Token this does not happen
Describe the expected behavior
the correct one would be for the controller to climb the new corridor normally using the Github APP
Whole Controller Logs
Whole Runner Pod Logs
Additional Context