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
Bug 1909821: Fix flexible scaling enablement #7643
Conversation
@afreen23: This pull request references Bugzilla bug 1909821, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
...components/ocs-install/internal-mode/install-wizard-steps/select-capacity-and-nodes-step.tsx
Outdated
Show resolved
Hide resolved
...rc/components/ocs-install/attached-devices/create-sc/wizard-pages/storage-and-nodes-step.tsx
Outdated
Show resolved
Hide resolved
f1bf7ae
to
65f2c59
Compare
@@ -109,9 +107,9 @@ export const StorageAndNodes: React.FC<StorageAndNodesProps> = ({ state, dispatc | |||
}, [cpu, dispatch, memory, nodesCount]); | |||
|
|||
React.useEffect(() => { | |||
const isFlexibleScaling: boolean = scNodeNamesLength && zonesCount < 3; | |||
const isFlexibleScaling: boolean = !!(nodesCount >= MINIMUM_NODES && zonesCount < 3); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I missed one more thing.
if arbiter is enabled the nodesCount is 3 and zones is 2, flexible sizing will get in place which should not happen. we need to check for if arbiter is enabled then flexible should not be enabled.
Also if you can move this logic to a single place so we don't need to change both always.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay arbiter is not for internal mode, so we can instead guard on arbiter itself.
We should not mix two diff logics. flexible scaling should stay intact.
I will make that change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for flexible scaling, we have single logic for internal & internal-attached.
attachedDevices
!!(nodesCount >= MINIMUM_NODES && zonesCount < 3)
internal
!!(nodesCount >= MINIMUM_NODES && zonesCount < 3)
we can place them somewhere in utils so we don't miss out other if there is a change in one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay I assumed the ask was for arbiter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @afreen23 looks much better now. :)
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1909821 Signed-off-by: Afreen Rahman <afrahman@redhat.com>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afreen23, cloudbehl 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 |
/test analyze |
1 similar comment
/test analyze |
/retest Please review the full test history for this PR and help us cut down flakes. |
6 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@afreen23: All pull requests linked via external trackers have merged: Bugzilla bug 1909821 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1909821
Signed-off-by: Afreen Rahman afrahman@redhat.com