This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1459344 - Multiselect element does not propagate to provision object
Multiselect element does not propagate to provision object
Status: ON_DEV
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate (Show other bugs)
Unspecified Unspecified
medium Severity medium
: GA
: cfme-future
Assigned To: Drew Bomhof
Depends On:
  Show dependency treegraph
Reported: 2017-06-06 17:22 EDT by Brant Evans
Modified: 2017-09-18 15:07 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brant Evans 2017-06-06 17:22:51 EDT
Description of problem:
With a service dialog that contains a drop-down element with Multiselect enabled the provision object does not contain the :dialog_element_name in prov.options hash. It is available from the prov.miq_request.options[:dialog] element, but the format is not easily consumed (key is Array::dialog_element_name and the value is a comma separated string).

In my case I have a dialog element called tower_jobs. To find the submitted contents I used the rails console.

Get the miq_provision object for the provision that was initiated:

prov = $evm.vmdb(:miq_provision,1000000000103)

print out the options of the provision object:

pp prov.options; nil

 :addr_mode=>["dhcp", "DHCP"],
 :placement_cluster_name=>[1000000000001, "Default"],
 :cluster_filter=>[nil, nil],
 :placement_auto=>[true, 1],
 :placement_dc_name=>[nil, nil],
 :number_of_vms=>[1, "1"],
 :src_vm_id=>[1000000000014, "RHEL-7.2-with-tower"],
 :provision_type=>["native_clone", "Native Clone"],
 :linked_clone=>[nil, nil],
 :pxe_server_id=>[nil, nil],
 :schedule_type=>["immediately", "Immediately on Approval"],
 :vm_auto_start=>[true, 1],
 :schedule_time=>Wed, 31 May 2017 15:20:00 UTC +00:00,
 :retirement_warn=>[604800, "1 Week"],
 :stateless=>[false, 0],
 :disk_format=>["default", "Default"],
 :cores_per_socket=>[1, "1"],
 :network_adapters=>[1, "1"],
 :name=>"RHEL 7",
 :description=>"RHEL 7",
 :available_catalogs=>[["VTC", 1000000000001]],
   1000000000002=>"Provision VM"},
 :placement_host_name=>[nil, nil],
 :placement_ds_name=>[nil, nil],
 :src_ems_id=>[1000000000001, "RHEV"],
 :customization_template_id=>[nil, nil],
 :miq_force_unique_name=>[true, 1],
 :vm_notes=>"Owner:  \nEmail: \nSource Template: RHEL-7.2-with-tower",
 :dest_cluster=>[1000000000001, "Default"],
 :networks=>[{:network=>"rhevm", :mac_address=>nil}]}

Notice that there is no :dialog_tower_jobs

Look at the dialog options on the request:

pp prov.miq_request.options[:dialog]; nil

 "Array::dialog_tower_jobs"=>"* Install PostgreSQL Server,*_Install_Apache"}

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


How reproducible:


Steps to Reproduce:
1. Create Service Dialog with a Multiselect enabled drop-down
2. Create Catalog Item to provision a VM using Service Dialog
3. Provision VM from Service Catalog
4. Inspect provision object via rails console or have automate method that logs the provision and request objects options.

Actual results:
dialog element NOT present in options of provision object

Expected results:
dialog element IS present in options of provision object

Additional info:
Comment 2 Dave Johnson 2017-06-12 16:33:43 EDT
Brant, please fill in severity, ie. what is the customer impact with this one?  Currently setting to medium but please weigh in if you feel its higher than that.

Use this as a guide...
Comment 3 Brant Evans 2017-06-12 19:59:38 EDT

I agree with the medium severity. I am able to work around the issue by getting the data from the request object.

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