Description

Steps to reproduce:
Create a VMware compute resource
Create a compute profile without thin provisioning checked
Save
Open compute profile again
Expected results:
when I open the compute profile, thin provisioning should not be checked
When I create a new host based on the compute profile, thin provisioning should not be checked
Actual results:
when I open the compute profile, thin provisioning is checked.
When I create a new host based on the compute profile, thin provisioning is checked

----

This behavior is seen accross most resources, NIC type, SCSI controller

The strange thing is that according to the production.log it seems we are actually changing the parameters:

Started PUT "/compute_profiles/5-redhat-6/compute_attributes/3" for 10.135.76.203 at 2014-05-09 13:31:14 -0500
Processing by ComputeAttributesController#update as */*
  Parameters: {"utf8"=>"â", "authenticity_token"=>"Ro9asdf62U4aOtUdm30G7asdghM7aW9asdfCZU/2Klbdf0573AavM=", "compute_attribute"=>{"vm_attrs"=>{"cpus"=>"1", "corespersocket"=>"1", "memory_mb"=>"1024", "cluster"=>"Cluster-A", "path"=>"/Datacenters/Cluster-A/vm", "guest_id"=>"rhel6_64Guest", "interfaces_attributes"=>{"new_interfaces"=>{"type"=>"VirtualE1000", "network"=>"network-1615", "_delete"=>""}, "0"=>{"type"=>"VirtualVmxnet3", "network"=>"network-109344", "_delete"=>""}}, "volumes_attributes"=>{"new_volumes"=>{"datastore"=>"esxhostA:Storage", "name"=>"Hard disk", "size_gb"=>"10", "thin"=>"true", "_delete"=>""}, "0"=>{"datastore"=>"esxhostA:Storage", "name"=>"Hard disk", "size_gb"=>"10", "thin"=>"false", "_delete"=>""}}, "scsi_controller_type"=>"ParaVirtualSCSIController", "image_id"=>"Templates/UNIX/RedHat/x86_64/6.5_x86_64"}}, "compute_profile_id"=>"5-redhat-6", "id"=>"3"}
Successfully decrypted field for Foreman::Model::Vmware vmware
Redirected to https://foremanhost.com/compute_profiles/5-redhat-6
Completed 302 Found in 66ms (ActiveRecord: 3.4ms)


This could be related to bug 4159