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

Bug 1488005

Summary: [UI] - VM's vNIC - Align the '+' and '-' buttons for the new Network Filter Parameters ability
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: low    
Version: 4.2.0CC: bugs, danken
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: 4.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 10:45:26 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
screenshot none

Description Michael Burman 2017-09-04 05:58:55 UTC
Created attachment 1321678 [details]
screenshot

Description of problem:
[UI] - VM's vNIC - Align the '+' and '-' buttons for the new Network Filter Parameters ability.

As we added the ability to add network filter params, we need to align the '+' and '-' buttons to the 'Name' and 'Value' fields.  

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

How reproducible:
100%

Steps to Reproduce:
1. Edit or create new VM's vNIC

Actual results:
Name and Value not aligned with add and remove buttons

Comment 1 Michael Burman 2017-10-23 05:59:01 UTC
Verified on - 4.2.0-0.0.master.20171022103432.gitaf9d8b6.el7.centos

Comment 2 Sandro Bonazzola 2017-12-20 10:45:26 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.