Bug 1269834

Summary:	RFE: Use "default" profiles (disk, network, cpu) when a profile is not explicitly defined
Product:	[oVirt] ovirt-engine	Reporter:	Daniel Helgenberger <daniel.helgenberger>
Component:	RestAPI	Assignee:	Doron Fediuck <dfediuck>
Status:	CLOSED DEFERRED	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.5.4	CC:	amureini, bugs, daniel.helgenberger, dfediuck
Target Milestone:	---	Keywords:	FutureFeature, RFE
Target Release:	---	Flags:	rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-26 08:42:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.