-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Superuser Creation: backend-server
does not have a host assigned
#7892
Comments
Hello, we've have a similar issue if not the same issue. Out of curiosity, where are you deploying your k8s cluster and how many resources does it have? We are currently using a GCP K8s cluster and the backend pods send an error that there are not enough resources for initialization. |
I am using AKS with four nodes, although only one is being allocated to the running pods. Our deployments do sound similar. I have not been able to work more on this, but will be picking this back up next sprint. |
@ifTaylor I'm also deploying on AKS. The reason the For me, the reason it was stuck in Pending state was the fact that PVCs where created with storageClass azure disk, which does not support ReadWriteMany access mode. The azure file class does, however. |
@mathijscarlu Thanks for the insight! That let me to the right spot in the By uncommenting the
Still not able to create superuser though.
|
@ifTaylor Feel free to check out my issue linked above and verify if you are having the same issue. |
Actions before raising this issue
Steps to Reproduce
values.yaml
Chart.yaml
$ helm upgrade -n cvat latest -i --create-namespace ./helm-chart -f ./helm-chart/values.yaml
Expected Behavior
Superuser made and
cvat-backend
container inbackend-server
pod not at a Waiting state.Possible Solution
No response
Context
Output when trying to create superuser:
Error from server (BadRequest): pod latest-backend-server-78b9bfb9f9-gpq98 does not have a host assigned
Pod status:
I've had this working before with a different CVAT version and the CrashLoopBackOff was resolved when creating the superuser.
Environment
- Using Kubernetes.
The text was updated successfully, but these errors were encountered: