Bug 1376487

Description of problem:

In webadmin in create/edit There's an option to add a nic based on a vnic profile.
the description of the option: 'Instantiate VM network interfaces by picking a vNIC profile.'
In practice the behaviour of this option is not consistent with the API and not sure that it's working as it was designed to work.

1. Upon instance type creation the vnic_profile drop down list contains only EMPTY vnic_profile, while there are several vnic profiles in the system in practice. Creating the 'EMPTY' nic will result with a nic with the default values and cannot be edited in UI.
In the API there's no problem to add nics to the instance type with any vnic_profile existing in the system.

2. Edit instance type menu seems to block the option to add a new nic or chance the profile of the old one, again this doesn't reflect the behaviour of the API and furthermore the actual edit box of the profile name isn't greyed out and one can write anything in it (although it won't be saved anywhere).

Not sure what to expect from this option, either it should be limited and to such and such constraints and in that case it should be reflected in API, or the other way around and the webadmin behaviour should be aligned with that of the API.

Possible reason: a vnic profile will always be coupled with a certain network, which will always belong to a certain data center. An instance type has no data-center/cluster and so the list is empty because it probably searches in DC= None (didn't look at code yet, doesn't seem too crucial). 

In the API on the other hand I was free to add a nic to the instance type with any vnic_profile I wanted from any data center, this makes more sense for a system level component
and the system also knows how to dill with it when creating a vm from that instance type, it will show the nic that was created with the vnic pofile outside the vm's datacenter, but the profile is set to 'EMPTY', so the filter works in vm level.

Version-Release number of selected component (if applicable):
rhevm-4.0.4.2-0.1.el7ev.noarch

How reproducible:
always

No useful messages was found in the logs.