When image name is bogus, instantiate-time error is too vague to be helpful
Consider a profile that references a bogus image ID, like "FBSD103-64-STD".
If one tries to instantiate this profile, the instantiate-time error message is:
This profile will not work on any clusters. Please check your profile or parameters for errors. If you are sure they are correct, you can report the problem to firstname.lastname@example.org and make sure to link to the problematic profile.
This is true, and it is good to get an error message at this point—but the error message doesn't explain anything about the reason for the error.
The error message would be much more helpful to users if it could explain some reason for the failure, e.g.,
This profile will not work on any cluster because no cluster has an image named 'FBSD103-64-STD'."
This error message might be further improved, of course, or we might try harder to keep people from putting goofy image names in their RSpecs, but the main point of this ticket is to get more info into the instantiate-time error message.