Bug 1538642

Summary: [UI] - Adjust bond's icon and bad bond warning icon to the new NIC icon size
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.1.2CC: bugs
Target Milestone: ovirt-4.3.0Flags: rule-engine: ovirt-4.3+
Target Release: 4.3.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.0_alpha Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-13 07:48:11 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 2018-01-25 14:06:31 UTC
Created attachment 1386098 [details]
screenshot

Description of problem:
[UI] - Adjust bond's icon and bad bond warning icon to the new NIC icon size which was implemented in BZ 1483844.

We need a final adjustment for the bond icon and bad bond warning icon, i have missed this item when was helping Greg(ux team) to design and decide on the new icon size and the whole text in this NIC panel. 

- The bond icon should be adjusted for the new NIC icon size (make it smaller)
- The bad bond warning icon should adjusted according to this (it currently very small) 

Version-Release number of selected component (if applicable):
4.2.1.3-0.1.el7

How reproducible:
100

Steps to Reproduce:
1. Create bond mode 4(default) via the setup networks dialog

Additional info:
See for reference -  https://bugzilla.redhat.com/show_bug.cgi?id=1483844

Comment 1 Michael Burman 2018-10-07 14:26:45 UTC
Verified on - 4.3.0-0.0.master.20181003151714.gitdc00947.el7

Comment 2 Sandro Bonazzola 2018-11-02 14:36:09 UTC
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 release, it has been closed with a resolution of CURRENT RELEASE.

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

Comment 3 Sandro Bonazzola 2018-11-02 14:51:31 UTC
Closed by mistake, moving back to qa -> verified

Comment 4 Sandro Bonazzola 2019-02-13 07:48:11 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

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