Bug #5481
OpenNebula: Allows using LOCKED images
| Status: | Pending | Start date: | 10/19/2017 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 5.6 | |||
| Resolution: | Pull request: | |||
| Affected Versions: | OpenNebula 5.4.2 |
Description
If you create new image from the http source, and if it downloads really slowly, it stacks in LOCKED state.
This is really harmful, if you try to connect this image it will stack all your VM, in HOTPLUG state:
[Z0][VM][I]: New LCM state is HOTPLUG_PROLOG_POWEROFF [Z0][TM][E]: missing DISK mandatory attributes (SOURCE, TM_MAD, CLONE, DATASTORE_ID) for VM 5317, DISK 3 [Z0][LCM][E]: prolog_failure_action, VM in a wrong state
If you try to create new vm, it will stack in CLONING state, without any logs.
We need to refuse mounting any images in LOCKED state.