Bug 1314362 - Getting 500 if job invocation validation fails
Summary: Getting 500 if job invocation validation fails
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high vote
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Lukas Pramuk
URL: http://projects.theforeman.org/issues...
Depends On:
TreeView+ depends on / blocked
Reported: 2016-03-03 12:58 UTC by Marek Hulan
Modified: 2019-09-26 14:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-07-27 09:25:22 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Foreman Issue Tracker 14015 None None None 2016-04-22 15:54:09 UTC
Red Hat Product Errata RHBA-2016:1501 normal SHIPPED_LIVE Red Hat Satellite 6.2 Capsule and Server 2016-07-27 12:28:58 UTC

Description Marek Hulan 2016-03-03 12:58:42 UTC
When I submit new invocation without specifying search query I get 500 with validation message instead of form with error messages

Comment 1 Marek Hulan 2016-03-03 12:58:43 UTC
Created from redmine issue http://projects.theforeman.org/issues/14015

Comment 2 Marek Hulan 2016-03-03 12:58:48 UTC
Upstream bug assigned to mhulan@redhat.com

Comment 4 Bryan Kearney 2016-03-14 12:05:06 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/14015 has been closed
Marek Hulán
Applied in changeset commit:foreman_plugin|4df85451f721b62e0ef2e5488841303be8849e30.

Comment 6 Lukas Pramuk 2016-04-29 11:13:01 UTC


using manual reproducer based on description in comment #0reproducer:

1. Navigate to Monitor > Jobs - New Job (/job_invocations/new)

2. Fill in all required fields but leave Search query empty and hit Submit

3. Search query field has red border and is asking for input (instead of submitting incomplete data):
 "Must select a bookmark or enter a search query"

Comment 8 errata-xmlrpc 2016-07-27 09:25:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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