Agones controller does not remove deleted pod from game server list #678
Comments
markmandel
added
kind/bug
|
Deleting the Pod should delete the backing Logic is here: Sounds like we should add a e2e test here: Make sure it always works. |
|
Oh - I assume this was on 0.9.0-rc? |
|
No, it was on 0.8.1. 0.9.0-rc was crashing our matchamker so we had to revert it for QA, we are not sure why it was crashing our matchmaker, so I have not created an issue for that yet. Once I have time for investigation I will look into it, but approaching release, it might not be soon. |
|
Digging into this some more - deleting a standalone gameserver's pod will make the GameServer move to Unhealthy (it's essentially the same as a crash). If the GameServer belongs to a Fleet, then the GameServer should be recreated. Got some more e2e tests working on this. |
Context: googleforgames#678 Wrote tests to confirm that deletion of a GameServer's backing Pod would move a GameServer to `Unhealthy`.
Context: googleforgames#678 Wrote tests to confirm that deletion of a GameServer's backing Pod would move a GameServer to `Unhealthy`.
Context: googleforgames#678 Wrote tests to confirm that deletion of a GameServer's backing Pod would move a GameServer to `Unhealthy`.
|
So I wrote e2e tests in #684, and they all passed - does that match up to the context you were describing? |
Context: googleforgames#678 Wrote tests to confirm that deletion of a GameServer's backing Pod would move a GameServer to `Unhealthy`.
|
I forgot to mention that the deleted pod had an |
|
Cool - I'll make sure I test that as well! |
Context: #678 Wrote tests to confirm that deletion of a GameServer's backing Pod would move a GameServer to `Unhealthy`.
|
So you'll be pleased to know, that now that we have an e2e test, we can see this happens... sometimes. Trying to work out why it only happens sometimes though. Somehow managed to hit it just now manually). 😬 inconsistent bugs are the best. |
|
I think I see where this is... and it was... never really implemented? (or if it was, it was lost). Fixing it! |
There was only implementation of GameServer's being moved to Unhealthy on very specific Pod events (container crash, being unschedulable), but never on Pod removal as a whole. Also it was locked down to specific states, which made it very fragile. Reworked this so that any of the above now triggers a GameServer being moved to an Unhealthy state. Closes googleforgames#678
There was only implementation of GameServer's being moved to Unhealthy on very specific Pod events (container crash, being unschedulable), but never on Pod removal as a whole. Also it was locked down to specific states, which made it very fragile. Reworked this so that any of the above now triggers a GameServer being moved to an Unhealthy state. Closes googleforgames#678
There was only implementation of GameServer's being moved to Unhealthy on very specific Pod events (container crash, being unschedulable), but never on Pod removal as a whole. Also it was locked down to specific states, which made it very fragile. Reworked this so that any of the above now triggers a GameServer being moved to an Unhealthy state. Closes #678
|
I've had this happen to me a couple times in v1.0.0 |
|
@djsell - thanks for reporting! Please open a new issue with repro steps, so we can look into it 👍 |
I had a fleet of 2 game servers running, one of the game server was allocated, I deleted allocated server by running
kubectl delete pod pod-name-xyzthis deleted the pod but when retrieving fleet information it still showed that fleet had two game servers running and kept returning allocated server IP and PORT to which we couldn't connect because game server pod has been deleted. Is there any reason why agones does not detect deleted pods?The text was updated successfully, but these errors were encountered: