Bug 974963
| Summary: | Unable to schedule operation wich does not require any input parameters | ||
|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Libor Zoubek <lzoubek> |
| Component: | REST | Assignee: | Heiko W. Rupp <hrupp> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.8 | CC: | theute |
| Target Milestone: | --- | ||
| Target Release: | RHQ 4.9 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-03-26 08:32: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: | |
| Embargoed: | |||
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 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. |
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: