-
Notifications
You must be signed in to change notification settings - Fork 813
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
Fix for scaling split allocated GameServerSets #3292
Fix for scaling split allocated GameServerSets #3292
Conversation
Fixes bug wherein if a set of Allocations occurred across two or more GameServerSets that had yet to be deleted for a RollingUpdate (because of Allocated GameServers), and a scale down operation moved the Fleet replica count to below the current number of Allocated GameServers -- scaling back up would not move above the current number of Allocated GameServers. Or to put it another way, the current Fleet update logic didn't consider old GameServerSets with Allocated GameServers but a 0 value for `Spec.Replicas` as a complete rollout when scaling back up, so the logic went back into rolling update logic, and it all went sideways. This short circuits that scenario up front. Close googleforgames#3287
Build Failed 😱 Build Id: 2b7f75c6-f4fa-4ac5-808b-0ab90a9d3b22 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Weird errors on 1.27 generic, in and around:
Going to rerun and see if it's consistent. |
Build Failed 😱 Build Id: aa6c0174-57b7-475e-9096-986ca8a39e05 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gongmax, markmandel The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
Build Failed 😱 Build Id: baacce9a-28c2-4dc3-a31f-6359ecbce317 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
It's still the:
I think I'm going to lose the plot here. |
Build Failed 😱 Build Id: ea6bfebd-63d3-45cf-9d63-56c8461e8c38 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Succeeded 👏 Build Id: 5bfc0b1d-09e7-46e1-9c42-cd584ebe2575 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
What type of PR is this?
/kind bug
What this PR does / Why we need it:
Fixes bug wherein if a set of Allocations occurred across two or more GameServerSets that had yet to be deleted for a RollingUpdate (because of Allocated GameServers), and a scale down operation moved the Fleet replica count to below the current number of Allocated GameServers -- scaling back up would not move above the current number of Allocated GameServers.
Or to put it another way, the current Fleet update logic didn't consider old GameServerSets with Allocated GameServers but a 0 value for
Spec.Replicas
as a complete rollout when scaling back up, so the logic went back into rolling update logic, and it all went sideways.This short circuits that scenario up front.
Which issue(s) this PR fixes:
Close #3287
Special notes for your reviewer:
Found a weird Unit Test in there while I was at it. Fixed it.