Bug 1488005 - [UI] - VM's vNIC - Align the '+' and '-' buttons for the new Network Filter Parameters ability
Summary: [UI] - VM's vNIC - Align the '+' and '-' buttons for the new Network Filter P...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.2.0
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ovirt-4.2.0
: 4.2.0
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-04 05:58 UTC by Michael Burman
Modified: 2017-12-20 10:45 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 10:45:26 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
screenshot (40.39 KB, image/png)
2017-09-04 05:58 UTC, Michael Burman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 81690 0 master MERGED webadmin: Align Network Filter Parameters editor 2017-10-20 19:13:20 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.