Description of problem: Add ability to create new service templates using the Rest API Version-Release number of selected component (if applicable): 5.4.0.2.20150519003830_673f996 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Git hub link - https://github.com/ManageIQ/manageiq/issues/2123
changing status to POST as https://github.com/ManageIQ/manageiq/pull/12594 was merged
Verified with POST /api/service_templates { "name": "My Atomic Service Template", "service_type": "atomic", "prov_type": "vmware", "display": false, "config_info": { "service_template_request": true, "provision_type": ["vmware", "VMware"], "customize_enabled": ["enabled"], "miq_request_dialog_name": "miq_provision_vmware_dialogs_template", "catalog_id": "3", "st_prov_type": "vmware", "service_type": "atomic", "dialog_id": "4", "placement_auto": [true, 1], "number_of_vms": [1, "1"], "src_vm_id": [21, "damnSmallLinux"], "vm_name": "test_rest_aRZlFIJa3ZAAA", "schedule_type": ["immediately", "Immediately on Approval"], "src_ems_id": [1, "vSphere 6 (nested)"], "provision": { "fqname": "/Service/Provisioning/StateMachines/ServiceProvision_Template/CatalogItemInitialization", "dialog_id": 4 }, "retirement": { "fqname": "/Service/Retirement/StateMachines/ServiceRetirement/Default", "dialog_id": 4 } } }
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/RHSA-2017:1367