Bug 1463568 - [UI] - no vNIC Profile is created during a new network is created
Summary: [UI] - no vNIC Profile is created during a new network is created
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.1.1.8
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ovirt-4.2.0
: ---
Assignee: Dominik Holler
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On: 1459003
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-21 08:58 UTC by Dominik Holler
Modified: 2017-12-20 11:01 UTC (History)
3 users (show)

Fixed In Version:
Clone Of: 1459003
Environment:
Last Closed: 2017-12-20 11:01:59 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 78363 0 master MERGED webadmin: Fix handling of empty network name 2017-06-27 14:52:37 UTC

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