Description of problem:
  Provisioning to VMware from template image fails if Datastore Cluster selected in compute profile.


How reproducible:
Very

Steps to Reproduce:
  1. Create VMware compute profile with "Datastore Cluster" selected, you will see "Data Store" select box gets disabled.
  2. Navigate to New host page, select deploy on VMware with created compute profile.
  3. Navigate to "Virtual Machine" tab, you will see both "Datastore cluster" and "Data store" select boxes enabled

Actual results:
Error: Unable to save
Failed to create compute instance: InvalidArgument: A specified parameter was not correct: Datastore outside the pod is specified for a disk to be placed inside the pod.
Host parameters in foreman/production.log contain both "storage_pod" and "datastore" values.


Expected results:
Host creation should succeed. 
I think host parameters should only contain either "storage_pod" or "datastore" values, not both.


Additional info:
  This probably happens because the disabling of "Data Store" select box on compute_profile form is controlled by onChange event on "Datastore cluster" select box and 'ContentLoad' trigger which is triggered in application.js. When this form is called by ajax by the "New host" form that trigger is not triggered and "Data Store" select box remains enabled. 
  If some other "Datastore cluster" is selected and then the original one is reselected the "Data store" select box gets disabled (by the onChange event) and installation succeeds.