No validation on input storage size compute profile
|Target version:||Team Marek backlog|
|Found in release:||Pull request:|
|Velocity based estimate||-|
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1193306
Description of problem:
The "Size (G)" field has no validation. You can enter anything you like and it will be stored. I made the mistake to specify 8GB and not 8G. It accepted it, but it failed to provision. IT took quit some time to figure out what was wrong.
Version-Release number of selected component (if applicable):
Enter anything you like in compute profile -> Storage -> Size.
Steps to Reproduce:
Everything is accepted
Only positive integers should be accepted (the G in the field description "Size (G) already has the unit).
#4 Updated by Marek Hulán over 1 year ago
- Category changed from Compute resources - libvirt to Compute resources
- Target version set to Team Marek backlog
Same thing for oVirt (and probably others) and not only compute profiles but also in host form. The reason is probably the fact that we don't have normal model attribute for that but we serialize volume_attributes as a hash. We should create a non-persistent model for volume and each compute resource should provide mapping methods.