Bug 1464750

Summary: [New UI] - New vNIC profile created on the wrong logical network
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: Frontend.WebAdminAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: high Docs Contact:
Priority: high    
Version: 4.2.0CC: bugs, danken, gshereme, oourfali
Target Milestone: ovirt-4.2.0Keywords: Regression
Target Release: ---Flags: rule-engine: ovirt-4.2+
rule-engine: blocker+
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 10:45:29 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:
Embargoed:
Attachments:
Description Flags
record1 none

Description Michael Burman 2017-06-25 12:16:06 UTC
Created attachment 1291699 [details]
record1

Description of problem:
[New UI] - New vNIC profile created on the wrong logical network.

When creating new vNIC profile, it is created on the wrong network. 
It seems that when creating a new vNIC profile under network, it pointing to the first network in the drop down list and not to the chosen/correct network in which you desire to create the vNIC. Because of that, the new vNIC created under the wrong network(the first one in drop down list).

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20170624071949.gitff9611b.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Create new network 'net1'
2. Try to create new vNIC profile under 'net1', press the network and create new vNIC profile called 'net11' under 'net1'

Actual results:
New vNIC profile 'net11' was created under network 'ovirtmgmt' and not under network 'net1' as it should.
'ovirtmgmt' was the grayed out network in the drop down list(see record) on the new vNIC dialog and not 'net1' as should to be(cause we choose net1 and not ovirtmgmt). As we choose to create the new vNIC under 'net1'

Expected results:
Must work as expected.

Comment 1 Red Hat Bugzilla Rules Engine 2017-06-26 05:43:25 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 3 Michael Burman 2017-08-21 07:45:29 UTC
Verified on - 4.2.0-0.0.master.20170820180837.git59243e9.el7.centos

Comment 4 Sandro Bonazzola 2017-12-20 10:45:29 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.