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:
*** Bug 1076007 has been marked as a duplicate of this bug. ***
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
Another use-case for this RFE was brought up by ovirt-foreman integration: http://projects.theforeman.org/issues/7244#note-6
*** Bug 1157151 has been marked as a duplicate of this bug. ***
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
Patch https://gerrit.ovirt.org/#/c/43250/ is already merged in 3.6, and ready for verification.
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.
AFAIK either Bugzilla doesn't allow updating a submitted description/comment or I do nt have permission to do that.
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