Skip to content
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

UPSTREAM: <carry>: fix max cluster size calculation on scale up #47

Merged
merged 1 commit into from
Mar 7, 2019

Conversation

frobware
Copy link

@frobware frobware commented Mar 7, 2019

When scaling up the calculation for computing the maximum cluster size
does not take into account the number of any upcoming nodes and it is
possible to grow the cluster beyond the cluster
size (--max-nodes-total).

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1670695

When scaling up the calculation for computing the maximum cluster size
does not take into account the number of any upcoming nodes and it is
possible to grow the cluster beyond the cluster
size (--max-nodes-total).

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1670695
@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 7, 2019
@ingvagabund
Copy link
Member

/lgtm

@frobware
Copy link
Author

frobware commented Mar 7, 2019

This has been verified and tested by QE.

@sunzhaohua2, thanks for all the testing efforts over the past few days. 👍

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 7, 2019
@openshift-merge-robot openshift-merge-robot merged commit 642c114 into openshift:master Mar 7, 2019
@frobware
Copy link
Author

frobware commented Mar 8, 2019

Upstream PR: kubernetes#1771

@frobware frobware deleted the fix-bz-1670695-v2 branch March 22, 2019 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants