Bug 1371537 - Cannot assign a vNIC profile for VM instance profile.
Summary: Cannot assign a vNIC profile for VM instance profile.
Keywords:
Status: CLOSED DUPLICATE of bug 1138431
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-30 12:28 UTC by Andrei Stepanov
Modified: 2016-09-01 09:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1770237 (view as bug list)
Environment:
Last Closed: 2016-09-01 09:25:07 UTC
oVirt Team: Virt
Embargoed:
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.