Service dialog create RHEV VM from template only passes default values

Automate
#1

I’ve downloaded the newest miq appliance and added RHV 4.1 as a provider.

I’ve created a service catalog where the user has to enter vm_name, and select memory and cpu cores from dropdowns. If I leave the defaults and provision the service the VM is provisioned with whatever value I have set the defaults to.

If I change the values in the dropdown the VM is provisioned with whatever the defaults were set to, ignoring my selection.

In my example here I have 8gb of mem and 6 cores set as defaults. The template in RHV is defined with 1gig of memory and 2 cores so miq is able to change these values in RHV when provisioning.

50%20PM
Screen Shot 2018-05-10 at 6.25.50 PM.png953×498 22.4 KB
14%20PM
Screen Shot 2018-05-10 at 6.26.14 PM.png926×401 20.9 KB
21%20PM
Screen Shot 2018-05-10 at 6.26.21 PM.png924×725 36.1 KB
06%20PM
Screen Shot 2018-05-10 at 6.27.06 PM.png984×466 28 KB

#2

I had the same problem as you. The way I fixed is to remove the default value from the dialog, I had 4096 as default so I ended up getting the same RAM no matter how I changed while ordering my catalog, and I then I started adding each element at a time, I don’t know why when I put all of them (CPU, RAM …) and the same time the default would be chose but when I tried adding one element at time and seeing if it get chosen over the defaults when I order the catalog.

#3

1st service provision using the dropdown defaults;
api.log:[----] I, [2018-05-10T22:18:28.582225 #2073:611f0c] INFO -- : MIQ(Api::ServiceCatalogsController.log_request) Parameters: {"action"=>"update", "controller"=>"api/service_catalogs", "format"=>"json", "body"=>{"option_0_vm_name"=>"miqtest015", "option_0_vm_memory"=>"8192", "option_0_cores_per_socket"=>"6", "option_0_number_of_sockets"=>"1", "action"=>"order"}}
automation.log:[----] I, [2018-05-10T22:18:49.719561 #1998:587140] INFO -- : Q-task_id([service_template_provision_task_67]) Instantiating [/Service/Provisioning/StateMachines/ServiceProvision_Template/CatalogItemInitialization?MiqServer%3A%3Amiq_server=1&Service%3A%3AService=23&ServiceTemplateProvisionTask%3A%3Aservice_template_provision_task=67&User%3A%3Auser=2&dialog_option_0_cores_per_socket=6&dialog_option_0_number_of_sockets=1&dialog_option_0_vm_memory=8192&dialog_option_0_vm_name=miqtest015&object_name=CatalogItemInitialization&request=clone_to_service&service_action=Provision&vmdb_object_type=service_template_provision_task]

2nd service provision changing the dropdowns to non-default values, default values still passed;
api.log:[----] I, [2018-05-10T22:18:52.519637 #2073:611c3c] INFO -- : MIQ(Api::ServiceCatalogsController.log_request) Parameters: {"action"=>"update", "controller"=>"api/service_catalogs", "format"=>"json", "body"=>{"option_0_vm_name"=>"miqtest016", "option_0_vm_memory"=>"8192", "option_0_cores_per_socket"=>"6", "option_0_number_of_sockets"=>"1", "action"=>"order"}}
automation.log:[----] I, [2018-05-10T22:19:21.753263 #2008:587140] INFO -- : Q-task_id([service_template_provision_task_70]) Instantiating [/Service/Provisioning/StateMachines/ServiceProvision_Template/CatalogItemInitialization?MiqServer%3A%3Amiq_server=1&Service%3A%3AService=24&ServiceTemplateProvisionTask%3A%3Aservice_template_provision_task=70&User%3A%3Auser=2&dialog_option_0_cores_per_socket=6&dialog_option_0_number_of_sockets=1&dialog_option_0_vm_memory=8192&dialog_option_0_vm_name=miqtest016&object_name=CatalogItemInitialization&request=clone_to_service&service_action=Provision&vmdb_object_type=service_template_provision_task]

#4

try using Radio Button, I don’t know for some reason using Radio Button instead of dropdown menu worked for me. Maybe it’s a bug or something else.