Bug #22409
closed
No validation for uuid in hammer compute-resource image creation
Description
Description of problem: While creating compute-resource image from CLI, there is no validation for option --uuid and passing any data in uuid, created image.
How reproducible: always
Steps to Reproduce:
1. hammer> compute-resource image create --compute-resource rhev_compute --name 'latest' --username 'root' --password 'dog8code' --architecture 'x86_64' --operatingsystem 'RedHat 7.3' --uuid '<any data>'
Image created
Actual results:
Image is created.
Expected results: Image should not create and raised error for passing valid uuid for images.
Additional info:
Updated by Akshay Mendhe over 6 years ago
- Subject changed from No validation for uuid in hammer compute-resource image creation to No validation for uuid in hammer compute-resource image creation
- Assignee set to Akshay Mendhe
Updated by Akshay Mendhe about 6 years ago
- Related to Bug #25081: No validation for image path in compute-resource image creation added
Updated by Lukas Zapletal about 6 years ago
- Triaged changed from No to Yes
Hello and thanks for the report. Most (if not all) compute resources use UUIDs, image path is only used for libvirt provider and this provider's API does not allow us to verify such a thing. So it cannot be done easily for libvirt, other providers should be able to verify UUID existance tho.