Bug 1314362

Summary:	Getting 500 if job invocation validation fails
Product:	Red Hat Satellite	Reporter:	Marek Hulan <mhulan>
Component:	Remote Execution	Assignee:	Marek Hulan <mhulan>
Status:	CLOSED ERRATA	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	bbuckingham, lpramuk, sthirugn
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/14015
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 09:25:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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

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

VERIFIED.

@Sat6.2.0-Beta-Snap9.3
tfm-rubygem-foreman_remote_execution-0.3.0.4-1.el7sat.noarch


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.

https://access.redhat.com/errata/RHBA-2016:1501