Bug 1269834 - RFE: Use "default" profiles (disk, network, cpu) when a profile is not explicitly defined
Summary: RFE: Use "default" profiles (disk, network, cpu) when a profile is not explic...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 3.5.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Doron Fediuck
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-08 10:28 UTC by Daniel Helgenberger
Modified: 2017-07-26 08:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-26 08:42:38 UTC
oVirt Team: SLA
Embargoed:
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)

Description Daniel Helgenberger 2015-10-08 10:28:44 UTC 
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.
Comment 1 Juan Hernández 2015-10-08 17:00:18 UTC 
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.
Comment 2 Doron Fediuck 2016-01-24 08:52:01 UTC 
Ping?
Comment 5 Doron Fediuck 2017-07-26 08:42:38 UTC 
We won't be perusing this issue any more. If someone needs it, patches are welcomed.
Note You need to log in before you can comment on or make changes to this bug.