Bug 1028829

Summary:	Leading Whitespaces in Task name in job XML not ignored
Product:	[Retired] Beaker	Reporter:	Amit Saha <asaha>
Component:	general	Assignee:	beaker-dev-list
Status:	CLOSED NOTABUG	QA Contact:	tools-bugs <tools-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	develop	CC:	aigao, asaha, dcallagh, ebaak, llim, qwan, rmancy
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-12 02:32:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.