Bug 1304928

Summary:	Job Matrix Reporting cannot parse J:123456
Product:	[Retired] Beaker	Reporter:	matt jia <mjia>
Component:	web UI	Assignee:	beaker-dev-list
Status:	CLOSED DUPLICATE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	mjia, tklohna
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-15 12:45:17 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 matt jia 2016-02-05 00:50:40 UTC

Description of problem:


Putting Job ID with J:12345 will introduce 500 internal error.

How reproducible:

easily

Steps to Reproduce:
1.Open the Job Matrix Report (Reports -> Matrix)
2. Put J:12345 into Job Id textbox and click generate button

Actual results:

500 internal error

Expected results:

J:12345 can be parsed and a matrix report can be generated.

Comment 1 Dan Callaghan 2016-02-05 03:09:46 UTC

(In reply to matt jia from comment #0)
> Expected results:
> 
> J:12345 can be parsed and a matrix report can be generated.

Expected result is just a better error message than 500. The problem is that it expects plain job IDs, not "taskspecs" like J:1234.

The job matrix job selection UI is really due for some attention, it's problematic in a number of ways (least of which this one...)

Comment 2 Tomas Klohna 🔧 2019-04-15 12:45:17 UTC


*** This bug has been marked as a duplicate of bug 1043419 ***