Bug 1028829 - Leading Whitespaces in Task name in job XML not ignored
Summary: Leading Whitespaces in Task name in job XML not ignored
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Beaker
Classification: Retired
Component: general
Version: develop
Hardware: Unspecified
OS: Unspecified
low
low vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-11 00:50 UTC by Amit Saha
Modified: 2018-02-06 00:41 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-12 02:32:13 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Amit Saha 2013-11-11 00:50:42 UTC 
Description of problem:

Let's say I (by mistake) specify a task name as:

<task name=" /CoreOS/beah_test_tasks/Sanity/reboot-behavior" >

Beaker will complain that the task doesn't exist even though "/CoreOS/beah_test_tasks/Sanity/reboot-behavior" task exists.



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


How reproducible:

Always


Steps to Reproduce:
1. See description above
2.
3.

Actual results:

Fails to find task

Expected results:

Beaker should check the task library after stripping the leading (and perhaps the following) whitespaces.

Additional info:
Comment 2 Amit Saha 2013-11-11 00:59:14 UTC 
Hmm I suspect, this will have implications elsewhere. The patch should consider that the tasks are then linked from the job results page and hence consider this before simply stripping off the whitespace.
Comment 3 Nick Coghlan 2013-11-12 02:32:13 UTC 
Whatever is generating the Job XML should ensure it uses actual task names.
Note You need to log in before you can comment on or make changes to this bug.