[GitHub] andrijapanicsb opened a new issue #3159: Not possible to edit/change a VMware VM immediately after it's stopped

[GitBox <gi...@apache.org>]

andrijapanicsb opened a new issue #3159: Not possible to edit/change a VMware VM immediately after it's stopped
URL: https://github.com/apache/cloudstack/issues/3159
 
 
   
   
   ##### ISSUE TYPE
   
   
    * Improvement Request
   
   
   ##### COMPONENT NAME
   
   VMWARE / vShpere code
   
   
   ##### CLOUDSTACK VERSION
   
   4.11.2 (didn't test all previous releases, except I know thing worked differently in 4.6)
   
   
   ##### CONFIGURATION
   
   vSphere hypervisor used.
   
   ##### OS / ENVIRONMENT
   NA
   
   
   ##### SUMMARY
   After VM is stopped via API/GUI, it's not possible to immediately change VM (resize disk, change Service Offering, etc. - these 2 were tested) since they require the VM to be stopped (and VM is actually stopped), but due to VMware code using "ping.interval" global setting value, it can take up to 2 x ping.interval for VM power state to be fully synced from vCenter to Management Server. ( by default, this becomes up to 2 minutes)
   
   
   ##### STEPS TO REPRODUCE
   
   Spin new VM, stop VM, and immediately try to change Service/Compute Offering for the VM.
   
   ##### EXPECTED RESULTS
   
   It should be possible to change/edit a VM immediately after stopping it (i.e. this was possible in ACS 4.6)
   
   ##### ACTUAL RESULTS
   Can't change Service/Compute offering or resize ROOT disk of a VM -  you will get error that it's impossible since VM is not stopped.
   
   ~~~
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services