Bug 1429810 - Fix the spurious leading space in the custom bond mode field
Summary: Fix the spurious leading space in the custom bond mode field
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.1.1.3
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ovirt-4.1.2
: 4.1.2
Assignee: Dominik Holler
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-07 07:03 UTC by Michael Burman
Modified: 2017-05-23 08:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-23 08:16:55 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.1+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 73644 0 ovirt-engine-4.1 MERGED engine: normalize bonding options without miimon 2017-03-09 08:36:53 UTC
oVirt gerrit 73645 0 ovirt-engine-4.1.1.z ABANDONED engine: normalize bonding options without miimon 2017-03-08 09:29:46 UTC

Description Michael Burman 2017-03-07 07:03:45 UTC
Description of problem:
[UI} - Fix the gap in the custom bond mode field.

The gap in the beginning of the custom bond mode field is leading to some issues when trying to edit the bond mode later on. 
Setting miimon parameter solving this space. 

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

How reproducible:
100

Steps to Reproduce:
1. Create custom bond mode via the setup networks dialog with mode=5 and approve operation
2. Edit the bond with mode=4


Actual results:
Failed. field colored in red. there is a gap/space in the beginning of the field. 

Expected results:
There should be no gap. 

Additional info:
See also which were affected with this 'cosmetic' bug - 
https://bugzilla.redhat.com/show_bug.cgi?id=1412563
https://bugzilla.redhat.com/show_bug.cgi?id=1424813

Comment 1 Michael Burman 2017-04-26 14:03:57 UTC
Verified on - 4.1.2-0.1.el7


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