Cannot edit a virtual disk to a VM using the "EDit VM Settings" dialog in vSphere Client due to the OK button not working
search cancel

Cannot edit a virtual disk to a VM using the "EDit VM Settings" dialog in vSphere Client due to the OK button not working

book

Article ID: 389337

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • When attempting to add a new disk to a powered on virtual machine (VM), the OK button for the "Edit virtual machine settings" is not working
  • There is no responsive even when clicking the button multiple times, only the CANCEL button is working
  • Other components like virtual network adapters can be added just fine.
  • Storage DRS (SDRS) is enabled for the datastore the virtual machine is on
  • The issue happens in different web browsers, clearing browser cache and cookies does not remediate the issue
  • When reviewing the vSphere Client localhost_access_log.txt in /var/log/vware/vsphere-ui/logs/access/, POST validate requests can be seen, but no matching apply requests:
    DATE/TIME] "POST /ui/mutation/validate/urn%3Avmomi%3AVirtualMachine%3A<VM_ID>%3####?propertyObjectType=com.vmware.vsphere.client.vm.VmConfigSpec HTTP/1.1" 200 <thread_ID> http-nio-5090-exec-2147 391
  • when reviewing the communication in the browser developer tab, DrsFaults with the message "No datastore in the datastore cluster is connected to the host that the virtual machine is on" can be seen:

 

 

Environment

VMware vCenter Server 7.0.3

Cause

This issue is caused by a fault in the vSphere Client UI logic for the VM settings dialog.

When an SDRS fault is generated, the UI gets stuck in faulty state and needs to be reinitialized by reopening the dialog.

This only affects vCenter Server 7.0.x, for vCenter Server 8.0.x the entire logic was rewritten and does not experience this problem.

Resolution

To work around the issue, close the "Edit VM settings" dialog using the CANCEL button. 

If the problem happens repeatedly, please review the Storage DRS configuration and fix any potential issues

Alternatively you can also mitigate this problem by upgrading to vCenter Server 8.0.x, where this problem does not exist.