Bug 1371537

Summary:	Cannot assign a vNIC profile for VM instance profile.
Product:	[oVirt] ovirt-engine	Reporter:	Andrei Stepanov <astepano>
Component:	Frontend.WebAdmin	Assignee:	bugs <bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.0.3	CC:	bugs, tjelinek
Target Milestone:	---	Flags:	rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1770237 (view as bug list)		Environment:
Last Closed:	2016-09-01 09:25:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andrei Stepanov 2016-08-30 12:28:11 UTC

In VM instance "edit" window, it is impossible to pick up any vNIC profile.

ovirt-engine-4.0.3-0.1.el7ev.noarch

1. Log in admin portal.
2. At the top-right press "Configure".
3. Select existing instance profile or create a new one.
4. Select "Edit instance type".
5. Press "Edit".
6. Select "General" tab.
7. Try to assign any values at "Instantiate VM network interfaces by picking a vNIC profile." section.

Actual results: there is not way to assign any vNIC.

In my opinion, if the there is no way to select vNIC, than there is no use to show it. Therefore, it can confuse a user.

Comment 1 Tomas Jelinek 2016-09-01 09:25:07 UTC

The reason is that the instance type is on "system" level so it does not know anything about the vnic profiles. On the other hand, we need some way how to configure the nics and the same widget as used for VM is reused also here.

The proper solution would be just have a way to set "number of nics" or similar instead of this add/remove widget. There is an RFE for that, so closing this as duplicate.

*** This bug has been marked as a duplicate of bug 1138431 ***