Bug 999969

Summary:	[RFE] Ability to create a VM with multiple NICs in a predictable order
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Moti Asayag <masayag>
Component:	ovirt-engine	Assignee:	Yevgeny Zaspitsky <yzaspits>
Status:	CLOSED ERRATA	QA Contact:	Meni Yakove <myakove>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	bazulay, danken, iheim, lpeer, mburman, myakove, nyechiel, pmukhedk, rbalakri, Rhev-m-bugs, sherold, yeylon, ylavi, yzaspits
Target Milestone:	ovirt-3.6.0-rc	Keywords:	AutomationBlocker, FutureFeature, Improvement
Target Release:	3.6.0	Flags:	nyechiel: Triaged+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-09 20:32:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1094012, 1157151, 1195039

Description Moti Asayag 2013-08-22 13:18:40 UTC

Description of problem:
Currently, the AddVm command creates a Vm without any interfaces.
AddVmFromTemplate creates the Vm with the exact interfaces as exist on the template. However, if the vnic profiles/networks are no longer exist, the nic will be created not attached to any network and a UpdateVmInterface command should be follow to adjust the vnic to the required one.
This can be avoided by allowing the AddVm and AddVmFromTemplate to provide a list of interfaces that the VM should be created with.

The can-do-action of the AddVm/AddVmFromTemplate should validate the correctness of the nics.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Moti Asayag 2014-03-16 12:16:31 UTC

*** Bug 1076007 has been marked as a duplicate of this bug. ***

Comment 3 Meni Yakove 2014-03-16 13:50:51 UTC

This is needed in order to run automation for Predictable_vNIC_Order.
http://liver.englab.brq.redhat.com/redirect/?url=http://wiki.ovirt.org/Feature/Predictable_vNIC_Order

Comment 4 Moti Asayag 2014-08-31 07:08:51 UTC

Another use-case for this RFE was brought up by ovirt-foreman integration:

http://projects.theforeman.org/issues/7244#note-6

Comment 5 Lior Vernia 2014-11-06 10:15:21 UTC

*** Bug 1157151 has been marked as a duplicate of this bug. ***

Comment 8 Yevgeny Zaspitsky 2015-07-07 15:20:16 UTC

The RFE is intended to provide a REST-API user a way to create a VM with predictable vNIC order. The ${header} is one of the available solutions for the problem. However REST-API maintainers are against this approach, so the implemented solution is to allow the REST-API user to invoke "reordermacaddresses" action explicitly.

URL: /vms/{vm:id}/reordermacaddresses

Comment 9 Dan Kenigsberg 2015-08-16 11:08:54 UTC

Patch https://gerrit.ovirt.org/#/c/43250/ is already merged in 3.6, and ready for verification.

Comment 11 Michael Burman 2015-11-18 13:55:41 UTC

Verified on - 3.6.0.3-0.1.el6

Yaniv, Yevgeny according to comment 8 above ^^ the summary of this RFE should be changed(origin summary not relevant). Please change it accordingly, thanks.

Comment 12 Yevgeny Zaspitsky 2015-11-18 14:12:55 UTC

AFAIK either Bugzilla doesn't allow updating a submitted description/comment or I do nt have permission to do that.

Comment 14 errata-xmlrpc 2016-03-09 20:32:25 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0376.html