Bug 1476010 - [RFE] Unable to reference vmware customization spec when deploying via REST API
Summary: [RFE] Unable to reference vmware customization spec when deploying via REST API
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: drew uhlmann
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-27 20:16 UTC by Ryan Spagnola
Modified: 2019-01-25 20:25 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-25 20:25:25 UTC
Category: Feature
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 4 Jillian Tullo 2017-10-17 17:24:14 UTC
Was able to verify that the value does get passed through properly from the API to MiqProvisionVirtWorkflow, but then the item is not found, resulting in a nil which writes that console output.

Passing along to Automate.

Comment 5 Greg McCullough 2017-11-20 19:32:40 UTC
Ryan - We never supported passing sysprep_custom_spec directly through the API call so I would say that part is an RFE.  (Do we want to use this ticket for the RFE or create a new one?)

The usual implementation is that the custom_spec is determined in automate or passed as part of the "additional_values" property to automate, then automate can call the "set_customization_spec" method.

See https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.5/html/methods_available_for_automation/chap_methods_available_for_use_with_cloudforms_management_engine#sect_vm_provision_task_miq_provision  (Search for "set_customization_spec")

Do you have any details on the work-around they implemented?  I assume it would be using the logic mentioned above.  I am not aware of any open issues around this feature.


Drew - We can discuss how to implement this directory from the API call.  I believe it will require refactoring the set_customization_spec method so that it can be called from the workflow.  See https://github.com/ManageIQ/manageiq/blob/master/app/models/mixins/miq_provision_mixin.rb#L186


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