Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1463568

Summary:	[UI] - no vNIC Profile is created during a new network is created
Product:	[oVirt] ovirt-engine	Reporter:	Dominik Holler <dholler>
Component:	BLL.Network	Assignee:	Dominik Holler <dholler>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.1.1.8	CC:	bugs, mburman, myakove
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1459003	Environment:
Last Closed:	2017-12-20 11:01:59 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:
Bug Depends On:	1459003
Bug Blocks:

Description Dominik Holler 2017-06-21 08:58:21 UTC

Description of problem:

If a new network is created, it is possible that the network is created without a vNIC profile

How reproducible:
100

Steps to Reproduce:
1. Open dialog "New Logical Network"
2. Type a Name
3. Type a Description
4. Delete the Name
5. Type a Comment
5. Apply with [OK]

Actual results:
Network is created without vNIC Profile

Expected results:
Network is created with vNIC Profile

Comment 1 Dominik Holler 2017-06-21 09:27:34 UTC

Steps to Reproduce:
1. Open dialog "New Logical Network"
2. Type a Name
3. Type a Description
4. Delete the Name
5. Type a Comment
6. Type a Name
7. Apply with [OK]

Comment 2 Michael Burman 2017-06-28 06:59:55 UTC

Verified on -  4.2.0-0.0.master.20170627181935.git9424f9b.el7.centos

Comment 3 Sandro Bonazzola 2017-12-20 11:01:59 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.