Bug #1009
Image stay in Locked state
| Status: | Closed | Start date: | 11/25/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Resolution: | invalid | Pull request: | ||
| Affected Versions: | OpenNebula 3.2 |
Description
Hi,
I have a problem. One VMs stop responding on commands with Persistent image. I used Sun-stone to "SHUTDOWN" and "Destroy" this machine. The VM was removed from list of running VMs. But something was going wrong and folder with images ("var/21/images") was not removed and image for VM get locked state.
A file transfer.0.delete was generated with content: "DELETE s2-8core:/var/lib/one/OpenNebula/var//21/images"
I am manually removed images folder but I cannot unlock an image.
How can I unlock the image?
The problems with removing an image could happened and it could be easily fixed manually.
I think it will be grate to add possibility to unlock images manually. I am sure that this image is ok because copy from it working well.
I am using OpenNebula 3.1
Thanks
History
#1
Updated by Ruben S. Montero over 9 years ago
- Status changed from New to Closed
- Assignee set to Ruben S. Montero
- Resolution set to invalid
You can use oneimage enable <image_id|image_name>
NOTE: OpenNebula behaves like this (requires user intervention to re-enable the image) because the shutdown process did not went well, so the image may need a manual fsck for example
Cheers