Bug 1552449
| Summary: | [UI] - Adjust VM's vNIC panel to the exact size of the host's NIC panel and align vNIC's icons to the center | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Michael Burman <mburman> | ||||||
| Component: | BLL.Network | Assignee: | Ales Musil <amusil> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 4.2.2 | CC: | bugs, gshereme, lveyde, ylavi | ||||||
| Target Milestone: | ovirt-4.2.4 | Flags: | rule-engine:
ovirt-4.2+
ylavi: exception+ |
||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | ovirt-engine-4.2.4.1 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-06-26 08:37:58 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
Michael Burman
2018-03-07 07:51:17 UTC
I suppose we can narrow down the height of each vnic panel in 4.2.z, can we? Ales, the VM's vNIC panel now is narrower than the host's NIC, not sure if it's by propose? in my opinion it's to much narrow now, looks like it got cut in the bottom. Created attachment 1442207 [details]
screenshots
Btw, the icons are broken as well, see BZ 1582824 > I would like to request a final adjustment(promise)
Your improvements have been extremely valuable. Please don't be shy!
Verified on - 4.2.4.1-0.1.el7 This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.4 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. |