Bug 1252793 - "Trimming white characters" in messages should be improved for clarity
Summary: "Trimming white characters" in messages should be improved for clarity
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: ---
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-12 09:11 UTC by Yuko Katabami
Modified: 2016-03-27 08:25 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-27 08:25:53 UTC
oVirt Team: Virt
Embargoed:
mgoldboi: ovirt-future?
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?


Attachments (Terms of Use)

Description Yuko Katabami 2015-08-12 09:11:23 UTC
Description of problem:
oVirt project has the following error messages:

Cannot ${action} ${type}. Linux boot parameters contain trimming whitespace characters.

This field can't contain trimming whidtespace characters.

"trimming whitespace characters" does not make clear sense.

Version-Release number of selected component (if applicable): 3.6


How reproducible: 100%



Actual results:
trimming whitespace characters

Expected results:
whitespace characters that require trimming
or
leading/trailing whitespace characters
(depending on what what sort of whitespace characters that should not be contained)


Additional info:

Comment 1 Einav Cohen 2015-08-13 08:14:57 UTC
see ovirt devel e-mail thread [1] for more details. 

[1] http://lists.ovirt.org/pipermail/devel/2015-August/011190.html

Comment 2 Red Hat Bugzilla Rules Engine 2015-10-19 11:00:07 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Moran Goldboim 2016-03-27 08:24:06 UTC
postponing to future version due to capacity.

Comment 4 Moran Goldboim 2016-03-27 08:25:53 UTC
Second thought, I'm going to close this one, I don't think we will get to it in the near future.


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