Red Hat Bugzilla – Bug 1269834
RFE: Use "default" profiles (disk, network, cpu) when a profile is not explicitly defined
Last modified: 2017-07-26 04:42:38 EDT
Description of problem:
Currently, using the API to create a VM the action fails if for instance the CPU profile is not set but more than one profile exists in the cluster. (Eg "Error: action type cpu profile empty").
This behavior should be changed to default to the default profiles rather than fail the api call.
Also refer to BZ1262293.
We had this problem with disk profiles, and it was already solved, see bug 1160846. So the only remaining potential problem is with VNIC profiles. Did you have that problem? If that happens I'd say this is a bug rather than a RFE.
We won't be perusing this issue any more. If someone needs it, patches are welcomed.