Sorry to  bother everyone again. Currently I think this is a bug in OpenNebula; 
but before I file a bug report I want to make sure it's not a local problem 
with my installation here or a fundamental misunderstanding on my side of what 
should happen.

Thanks,
Carsten

From: [email protected] 
[mailto:[email protected]] On Behalf Of 
[email protected]
Sent: Friday, 4 March 2011 15:22
To: [email protected]
Subject: [ExternalEmail] Re: [one-users] saveas not always working

Some more insights after a bit more digging:

It seems to me that a successful save depends on the disk image(s) being moved 
from the .../var/XX/images directory to .../var/XX. This seems to happen during 
the shutdown epilog, but not during cancel or finalize.

Carsten

From: [email protected] 
[mailto:[email protected]] On Behalf Of 
[email protected]
Sent: Friday, 4 March 2011 14:53
To: [email protected]
Subject: [ExternalEmail] [one-users] saveas not always working

I use OpenNebula 2.0.1 with KVM as hypervisor. I issue an saveas command and as 
far as I understand things the image should be saved when the vm reaches the 
state DONE. From a state ACTIVE - RUNNING there seem to be 3 actions to get to 
DONE:

Shutdown: In this case the image gets saved and all is good.

Cancel, and finalize: In these cases the image hook is called, but it produces 
this error message:

Fri Mar  4 14:36:19 2011 [HKM][D]: Message received: LOG - 85 Command execution 
fail: /srv/cloud/one/share/hooks/image.rb 85
Fri Mar  4 14:36:19 2011 [HKM][D]: Message received: LOG - 85 STDERR follows.
Fri Mar  4 14:36:19 2011 [HKM][D]: Message received: LOG - 85 ExitCode: 255
Fri Mar  4 14:36:19 2011 [HKM][D]: Message received: EXECUTE FAILURE 85 image

The image is not saved, but its state is nevertheless set to READY.

I would like the image to successfully save in all 3 cases. Your help is much 
appreciated.

Thanks,
Carsten
_______________________________________________
Users mailing list
[email protected]
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Reply via email to