-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Issue with ShulkerSDK not returning game ID and failing to find available server after retry #809
Comments
Hello! The issue seems to be in the shulker-operator code. I am using grpcui to send an allocation request directly, and I am getting the same error
|
Hello! I have also checked the agones-allocator logs, and found this: |
The previous error was because, by default, the agones allocators expects the request to be TSL. You have to set the helm values agones.allocator.disableMTLS and agones.allocator.disableTLS to true. But now, there is a new error in the agones allocator: |
Hi! It turns out the issue was on my end. The problem was from the Agones allocator being configured to use both REST and gRPC on the same port. For some reason, HTTP took priority, causing an error to be returned to the Shulker operator, even though the request was made via gRPC. Once I disabled the HTTP server on the allocator, everything started working as expected. |
Hi! I thought the issue was fixed, but it isn't. When no server is available, and the summonIfNeeded parameter is true, the shulker sdk gives the following error:
|
Hi @jeremylvln, |
Hi @Andrei965! Thanks for pinging me, I've totally forgot about your issue. I'll manage to take a look this week :) |
What happened?
I'm running a Shulker Kubernetes cluster and have implemented a custom matchmaking microservice in Kotlin. I'm using the ShulkerSDK to allocate a server, calling the following method:
The issue I'm facing is that while the code successfully creates the game server, it doesn't return the game ID as expected. Instead, it throws an error. Additionally, when I run the code again, it fails to find an available server, even though a server exists with its game state set to "ready."
What components are involved in your issue?
Operator, Server Agent (Minestom)
Version
v0.11.0
Kubernetes Version
Client Version: v1.30.5 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.31.0
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: