Bug 1252793

Summary: "Trimming white characters" in messages should be improved for clarity
Product: [oVirt] ovirt-engine Reporter: Yuko Katabami <ykatabam>
Component: Frontend.WebAdminAssignee: bugs <bugs>
Status: CLOSED WONTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: low Docs Contact:
Priority: low    
Version: ---CC: bugs, gklein, lsurette, mgoldboi, michal.skrivanek, rbalakri, yeylon, ykaul
Target Milestone: ---Flags: mgoldboi: ovirt-future?
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-27 08:25:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.