-
Notifications
You must be signed in to change notification settings - Fork 375
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
BUG: order-service stuck in CrashLoopBackOff state #101
Comments
How did you deploy the application? Did you use the |
I used |
Thanks for reporting the issue @engrashid. I've seen this error occur when the order-service's startupProbe fails (for whatever reason). However, it should resolve itself after the scheduler kills and restarts the pod. Does your order-service eventually come up? If not, you can try running the following command to restart:
Also, if you run the following command, you might be able to see some additional detail that could help troubleshoot.
|
@engrashid do you still need assistance here? |
Describe the bug
order-service deployment fails in aks cluster
To Reproduce
Steps to reproduce the behavior:
kubectl get pods -n pets | grep order-service
Expected behavior
order-service-78d6dc9fbb-7kvnz 0/1 CrashLoopBackOff 17 (4m13s ago) 43m
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: