| Summary: | vm provisioning using REST API fails with automation engine errors | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Martin Kourim <mkourim> |
| Component: | Automate | Assignee: | Drew Bomhof <dbomhof> |
| Status: | CLOSED WORKSFORME | QA Contact: | Martin Kourim <mkourim> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.6.0 | CC: | gmccullo, jhardy, mkanoor, mkourim, obarenbo, tfitzger |
| Target Milestone: | GA | ||
| Target Release: | cfme-future | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | automate:rest:provisioning | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-23 22:24:42 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: | |
Martin, can you confirm if this is on 5.7 or not? I was not able to reproduce it on 5.7 Removing blocker flag as this is not a bug on 5.7. Martin - Please retest for 5.6.3. Retested on 5.6.3 and I can no longer reproduce this issue. Martin - would it be ok to close this issue since it seems fixed in 5.6.3 and up? Yes, I'm ok with closing this. |
Description of problem: Provisioning of VM using REST API fails with automation engine errors. Version-Release number of selected component (if applicable): 5.6.2.2 How reproducible: 100% Steps to Reproduce: 1. provision VM using REST API with request like POST /api/provision_requests { "action":"create", "resource":{ "version":"1.1", "template_fields":{ "guid":"<guid>" }, "vm_fields":{ "vm_name":"<name>", "number_of_cpus":1, "vm_memory":"2048", "vlan":"VM Network" }, "requester":{ "user_name":"admin", "owner_first_name":"John", "owner_last_name":"Doe", "owner_email":"jdoe", "auto_approve":true }, "tags":{ "network_location":"Internal", "cc":"001" }, "additional_values":{ "request_id":"1001" }, "ems_custom_attributes":{ }, "miq_custom_attributes":{ } } } 2. check provisioning progress: GET /api/provision_requests/:id 3. check evm.log Actual results: Provisioning fails with "[RuntimeError]: A specified parameter was not correct. \nspec.location.folder". In evm.log: ERROR -- : Q-task_id([miq_provision_63]) <AutomationEngine> State=<CheckProvisioned> running on_error raised exception: <invalid method calling syntax: [update_provision_status(status => '[RuntimeError]: A specified parameter was not correct. spec.location.folder')]> Relevant log snippets on http://pastebin.test.redhat.com/424905