Public bug reported:

As we know that in cinder, volume size cannot be a decimal value, only integer 
values are accepted.
So when a user create a volume from horizon,horizon allows user to enter a 
decimal value or negative value  in Size (GiB) field.
obviously, user can't create a volume in decimal size as there are some 
validation on create button,
But we can enforce more validation on the volume Size field (like user can't 
enter alphabets which is currently enforced), we shouldn't allow negative 
symbol '-' and decimal point '.' in the field too, So the user can only enter 
number from (0-9).

** Affects: horizon
     Importance: Undecided
     Assignee: Vishal Manchanda (vishalmanchanda)
         Status: New

** Changed in: horizon
     Assignee: (unassigned) => Vishal Manchanda (vishalmanchanda)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1803486

Title:
  Floating and negative values accepted in volume size field.

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  As we know that in cinder, volume size cannot be a decimal value, only 
integer values are accepted.
  So when a user create a volume from horizon,horizon allows user to enter a 
decimal value or negative value  in Size (GiB) field.
  obviously, user can't create a volume in decimal size as there are some 
validation on create button,
  But we can enforce more validation on the volume Size field (like user can't 
enter alphabets which is currently enforced), we shouldn't allow negative 
symbol '-' and decimal point '.' in the field too, So the user can only enter 
number from (0-9).

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1803486/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to