Bug 1032063

Summary: Add network interface not included in Guide me and no inteface is created automaticaly
Product: Red Hat Enterprise Virtualization Manager Reporter: Dušan Kajan <dkajan>
Component: ovirt-engine-webadmin-portalAssignee: Lior Vernia <lvernia>
Status: CLOSED NOTABUG QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acathrow, bazulay, ecohen, iheim, lsvaty, lvernia, masayag, pstehlik, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-24 14:05:39 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:

Description Dušan Kajan 2013-11-19 13:34:17 UTC 
Description of problem:
In 3.3 the network interface was created automatically after creation of VM (and in Guide Me was included option of adding new one). In current state, there is none of these options - NI have to be added from different subtab, and no default NI is created.

Version-Release number of selected component (if applicable):
rhevm-setup-3.3.0-0.33.beta1.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create New VM

Actual results:
No interface is created and no Add New Network Interface option in Guide Me

Expected results:
In Guide Me there should be Add New Network Interface option, default interface should be created

Additional info:
Comment 1 Lior Vernia 2013-11-24 14:05:39 UTC 
Network interfaces can be created straight from the Add VM dialog. That's why the network interfaces have been removed from the Guide Me sequence, see Bug 1024249.
Comment 2 Dušan Kajan 2013-11-26 09:00:31 UTC 
ok, i miss that, anyway it is still not created automatically (default option in New VM dialog is empty/empty), this should be change to rhevm/rhevm, should I open new bug for it, or proceed with this one?
Comment 3 Lior Vernia 2013-11-26 09:29:14 UTC 
The current behavior is that if the chosen template's profiles are available, then they're the ones attached by default to the interfaces. If they're not available, the NICs are created but no profile is attached to them.

It is not clear that attaching rhevm/rhevm by default is better. If users want that profile to be attached to the NICs by default, they can attach it to the template's NICs. And if we do decide that it's better to try and "guess" which profile should be attached, maybe the logic should be more complicated? Maybe try to pick another profile of the original network? And what if the original network has been removed from the DC in the meantime, should we maybe try to look for a different network (different ID) with the same name? The "correct" behavior is ill-defined in my opinion, and it's very arguable that any behavior would actually be better than the current one.
Comment 4 Lukas Svaty 2013-11-26 14:22:19 UTC 
when you moved network interface into the VM-creation tab, is it appropriate to still leave disk creation in separate tab or can that be also move to VM-creation tab?
Comment 5 Lior Vernia 2013-11-26 14:30:12 UTC 
Well, I would say this isn't the most natural place for either of them. Enabling network interface configuration in this dialog had a very specific purpose, to support the instance type feature (http://www.ovirt.org/Features/Instance_Types). My point being, that the general goal isn't to move as much logic as possible into the VM creation dialog.