Bug #4266
Uploading big image via sunstone got error message
| Status: | New | Start date: | 12/23/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Sunstone | |||
| Target version: | - | |||
| Resolution: | Pull request: | |||
| Affected Versions: | OpenNebula 4.14 |
Description
[ImageAllocate] Error allocating a new image. NAME is already taken by IMAGE 34.
After all this image is uploaded successfully.
It looks like in some case (probably some timeout) sunstone tries register again image (after successful upload).
Related issues
History
#1
Updated by Rolandas Naujikas over 5 years ago
At least it is for the case when BRIDGE_LIST is used.
#2
Updated by Ruben S. Montero over 5 years ago
- Target version set to Release 5.0
#3
Updated by Anton Todorov over 5 years ago
Hi,
I hit similar issue when defining new datastore. It was with same wording, but for the DATASTORE name. The datastore was created and I was in a hurry to reproduce/catch another issue so I do not take enough care for the message.
It occurred on sunstone process running on highly loaded CPU core so with high probability it is some timeout or race condition during high load?
Regards,
Anton Todorov
#4
Updated by Carlos Martín about 5 years ago
- Related to Bug #4430: Error allocating a new image. NAME is already taken added
#5
Updated by Carlos Martín about 5 years ago
- Target version changed from Release 5.0 to Release 5.2
#6
Updated by Carlos Martín almost 5 years ago
- Status changed from Pending to New
- Target version deleted (
Release 5.2)