-
Notifications
You must be signed in to change notification settings - Fork 161
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
[CDS-102291] Update CrashLoopBackoff roubleshooting #8324
Conversation
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://671200a4caaedf5d4eda5838--harness-developer.netlify.app |
### Issue: GitOps agent pod stuck in CrashLoopBackoff | ||
## Error: GitOps agent pod stuck in CrashLoopBackoff | ||
|
||
### Issue: This is an unauthorized agent. Sleeping for 15 minutes and then shutting down, please check your settings on HarnessUI | ||
|
||
The GitOps agent goes into a CrashLoopBackoff state due to an authentication failure with the GitOps service. This issue occurred as the token in the agent’s YAML did not match the public key in the GitOps service database. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we also reword this.
something like "This error occurs when" instead of "The GitOps agent goes into CrashLoopBackoff"
It will be more clear and specific
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6712320b657e769c6b68f952--harness-developer.netlify.app |
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged: