Description of problem:
When user attempts to edit Custom flavor via 'Edit Flavor' dialog in VM Overview page, the value in CPU/RAM fields cannot be fully deleted. It always contains at least value 1.
It means that when a user wants to change CPU count from 1 (which is default)
to 2, it's necessary to first append number 2 (meaning now the field contains value 12) and then delete the number 1. Same goes to the RAM field.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
at one hand it is not really incorrect since the validation does not allow this field to be empty (e.g. if you pressed a letter it would also not print it). On the other hand, the VM wizard does allow in those fields empty strings. So we should decide which one is correct and unify.
I agree this feels a bit strange. Can we not validate the fields when they are empty when they attempt to save/move forward and require values?
(In reply to Matt from comment #2)
> I agree this feels a bit strange. Can we not validate the fields when they
> are empty when they attempt to save/move forward and require values?
yes, this is how we do it in the VM wizard. OK, so we should do the same here as well, ack.
It's still cannot be fully deleted, but user can draw the mouse over "1", then it has a shadow on the number, then can replace with any other value.
As the design it is, move the bug to verified.
This one landed only in 4.5, 4.4 is still broken
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.