Bug #1473
[VMWARE] driver resume/restore using wrong deployment file
Status: | Closed | Start date: | 09/13/2012 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | Tino Vázquez | % Done: | 100% | |
Category: | Drivers - Auth | |||
Target version: | Release 3.8 | |||
Resolution: | fixed | Pull request: | ||
Affected Versions: | OpenNebula 3.6 |
Description
When resuming a stopped VM, the restore function in /var/lib/one/remotes/vmm/vmware/vmware_driver.rb always use deployment.0 file to (re)deploy the VM.
This causes the resume to fail if the VM did not start at the first submission and the file deployment.0 does not exists.
def restore(checkpoint) begin # Define the VM dfile = VAR_LOCATION + "/" + --> File.basename(File.dirname(checkpoint)) + "/deployment.0" rescue => e OpenNebula.log_error("Cannot open checkpoint #{e.message}") exit -1 end deploy_id = define_domain(dfile) ...
History
#1 Updated by Tino Vázquez almost 9 years ago
- Status changed from New to Closed
- Assignee set to Tino Vázquez
- % Done changed from 0 to 100
- Resolution set to fixed
Pick the last deployment file