Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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. 

Version-Release number of selected component (if applicable): satellite 6.3 snap 25


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:

Created redmine issue http://projects.theforeman.org/issues/22409 from this bug

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/22409 has been resolved.

This request is a too complex change in core as every CR uses a different key (UUID, image path etc).