Description of problem:

When attempting to associate a vm to a compute resource, the uuid of the vm is supposed to be used.  If a user doesn't provide the uuid, and instead provides the foreman host id (by accident), the error message is misleading.

This is an example of trying to associate a vm by the foreman host id:

hammer compute-resource associate-vms --name my-compute-resource --vm-id 6
Could not associate the virtual machines:
  Resource compute_resource not found by id '1'

The message Resource compute_resource not found by id '1' makes it seem like the actual compute resource can not be found.

Also, the redundancy of using "resource compute_resource" is worded strangely, and doesn't have the affect of letting the end user know what happened.

It would be more helpful if the error message would say something like:

The vm with uuid '6' is not found on the compute_resource with id '1'

This would both let the user know they should use the "uuid", and also that the vm specifically isn't found on the compute resource.

How reproducible:

always when trying to associate a vm to a compute resource, using the wrong vm uuid

Is this issue a regression from an earlier version:

no