Bug 1526906 - [UI] - Align the 'Remove networks from external provider' checkbox in the remove network dialog
Summary: [UI] - Align the 'Remove networks from external provider' checkbox in the rem...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ovirt-4.2.1
: ---
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-18 07:57 UTC by Michael Burman
Modified: 2018-02-12 11:46 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-02-12 11:46:33 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+
ylavi: exception+


Attachments (Terms of Use)
screenshot (82.88 KB, image/png)
2017-12-18 07:57 UTC, Michael Burman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 85888 0 master MERGED webadmin: Fix wrong align of checkbox label in RemoveConfirmationPopup 2018-01-03 18:21:14 UTC

Description Michael Burman 2017-12-18 07:57:14 UTC
Created attachment 1369297 [details]
screenshot

Description of problem:
[UI] - Align the 'Remove networks from external provider' checkbox in the remove network dialog.

The 'Remove network(s) from the external provider(s) as well.' checkbox isn't aligned to the text in the remove logical network dialog.

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

How reproducible:
100%

Steps to Reproduce:
1. Import network from external provider to rhv
2. Remove the network from rhv

Comment 1 Michael Burman 2018-01-07 12:53:47 UTC
Verified on - 4.2.1-0.2.el7

Comment 2 Sandro Bonazzola 2018-02-12 11:46:33 UTC
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 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.


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