Description of problem: When trying to edit a host either Foreman or Katello side either in hammer or the webui we get the following: 2018-12-12T18:13:06 [W|app|5d66e] Failed to update a compute VMware (VMware) instance tom-lorusso.satellite.lab.eng.rdu2.redhat.com: NotSupported: The operation is not supported on the object. This is related to VMware hot add functionality on Memory with not being able to lower memory on a running host or increase it more than 3GB https://kb.vmware.com/s/article/2008405?lang=en_US Version-Release number of selected component (if applicable): Satellite 6.4.1 tfm-rubygem-fog-vsphere-2.3.0-1.el7sat.noarch foreman-1.18.0.39-1.el7sat.noarch How reproducible: Steps to Reproduce: 1. Install Satellite 6.4.x 2. Configure Compute Resource for VMware 3. Setup Compute Profile with 2GB of ram and hot add for cpu/mem 4. Create hostgroup and assign compute profile to hostgroup 5. Build VM with 4GB of ram 6. Try to change the content-view of host and it will fail with below Actual results: 2018-12-12T18:13:06 [W|app|5d66e] Failed to update a compute VMware (VMware) instance tom-lorusso.satellite.lab.eng.rdu2.redhat.com: NotSupported: The operation is not supported on the object. RbVmomi::Fault: NotSupported: The operation is not supported on the object. /opt/theforeman/tfm/root/usr/share/gems/gems/rbvmomi-1.10.0/lib/rbvmomi/vim/Task.rb:14:in `wait_for_completion' /opt/theforeman/tfm/root/usr/share/gems/gems/fog-vsphere-2.3.0/lib/fog/vsphere/requests/compute/vm_reconfig_hardware.rb:10:in `vm_reconfig_hardware' /opt/theforeman/tfm/root/usr/share/gems/gems/fog-vsphere-2.3.0/lib/fog/vsphere/requests/compute/update_vm.rb:31:in `update_vm' /opt/theforeman/tfm/root/usr/share/gems/gems/fog-vsphere-2.3.0/lib/fog/vsphere/models/compute/server.rb:298:in `save' /usr/share/foreman/app/models/compute_resources/foreman/model/vmware.rb:469:in `save_vm' Expected results: Host to be able to be changed either in regards to Foreman or Katello Additional info: The workaround is to set compute profile with hot add cpu/mem to disabled(unchecked) and change base ram to the minimum of what hosts are being built with. We already have the VM memory information from VMware in Host details under VM tab. We should be able to use that information and see what is being passed in the JSON on host edit and either stop the user and error in Foreman with a better error or adjust/ignore the memory/cpu change.
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in one month's time. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact your Red Hat Account Team. Thank you.