Bug 1304928 - Job Matrix Reporting cannot parse J:123456
Job Matrix Reporting cannot parse J:123456
Status: NEW
Product: Beaker
Classification: Community
Component: web UI (Show other bugs)
22
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: beaker-dev-list
tools-bugs
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-04 19:50 EST by matt jia
Modified: 2016-07-27 02:33 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description matt jia 2016-02-04 19:50:40 EST
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-04 22:09:46 EST
(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...)

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