Fixed field reset for memory & cpu fields in new tenant size screen #1593
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bexsoft
requested review from
Alevsk,
adfost,
dvaldivia,
harshavardhana,
jinapurapu and
prakashsvmx
Also fixed an issue with memory limit selection in create tenant Signed-off-by: Benjamin Perez <[email protected]>
bexsoft
force-pushed
the
fixed-cpu-memory-reset
branch
from
749bc50 to
20fe177
Compare
dvaldivia
approved these changes
Feb 17, 2022
adfost
approved these changes
Feb 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this do?
Fixed field reset for memory & cpu fields in new tenant size screen
Also fixed an issue with memory limit selection in create tenant
How does it look?
Signed-off-by: Benjamin Perez [email protected]