Bug #4739

vCenter: Guestinfo reconfiguration while the VM makes it unable to start again

Added by Javi Fontan over 4 years ago. Updated about 4 years ago.

Status:ClosedStart date:08/23/2016
Priority:NormalDue date:
Assignee:Javi Fontan% Done:

100%

Category:vCenter
Target version:Release 5.2
Resolution:fixed Pull request:
Affected Versions:OpenNebula 5.0

Description

When a guestinfo variable is added to a VM in poweroff state this is written to vmx file so it is persistent between boots. If this variable is set while the VM is running then it is converted to ephemeral. Deleted from the vmx file and after the VM is powered off it disappears.

This makes resuming a VM after poweroff impossible as the driver is trying to read the token from the context before starting the VM:

https://github.com/OpenNebula/one/blob/release-5.0.2/src/vmm_mad/remotes/vcenter/vcenter_driver.rb#L2364

guestinfo.opennebula.context should be set every time the VM is started. Also the tokes should be written somewhere else.

Associated revisions

Revision 19a7a760
Added by Javi Fontan over 4 years ago

bug #4739: store token outside of vmware guestinfo

History

#1 Updated by Javi Fontan over 4 years ago

  • Target version set to Release 5.2

#2 Updated by Tino Vázquez about 4 years ago

  • Status changed from Pending to Closed
  • Assignee set to Javi Fontan
  • % Done changed from 0 to 100
  • Resolution set to fixed

Also available in: Atom PDF