Bug 974963 - Unable to schedule operation wich does not require any input parameters
Summary: Unable to schedule operation wich does not require any input parameters
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: REST
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHQ 4.9
Assignee: Heiko W. Rupp
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-17 09:19 UTC by Libor Zoubek
Modified: 2015-11-02 00:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-26 08:32:17 UTC
Embargoed:


Attachments (Terms of Use)

Description Libor Zoubek 2013-06-17 09:19:46 UTC
Description of problem: I am not able to schedule operation wich does not require any input parameters via REST


Version-Release number of selected component (if applicable):
RHQ 4.8-master

How reproducible:always


Steps to Reproduce:
1. create a draft operation by POST /operation/definition/<OPDEF>?resourceId=<RES> where OPDEF is an operation definition for resource RES wich does not require any input params

as a response body you get something like this:

{u'name': u'viewProcessList', u'links': [{u'edit': {u'href': u'http://localhost:7080/rest/operation/1365575059'}}],
u'resourceId': 10001, u'definitionId': 10006, u'readyToSubmit': False, u'params': {}, u'id': 1365575059}

2. change 'readyToSubmit' to True
2. remove 'links' key from the body and POST it to operation/1365575059

Actual results: 

Scheduling fails with message

{u'message': u'Parameter Validation of parameters failed is bad: Definition is null'}

Expected results: Scheduling is successfull


Additional info:

Comment 1 Heiko W. Rupp 2013-07-25 15:31:30 UTC
master 83336d77e19

Incoming links are accepted and the api throws a 503 error if they do not follow the expected format. This has been implemented in master ddef8592f

Comment 2 Heiko W. Rupp 2014-03-26 08:32:17 UTC
Bulk closing now that 4.10 is out.

If you think an issue is not resolved, please open a new BZ and link to the existing one.


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