Ok, seems to work finally.
The error was because I deleted the test image thinking it will only remove infos from database whereas it has trully deleted the image in the storage node, even if it appeared in default() storage in image description.
Now, new image will be stored in the storage associate with the location of the captured machine despite the selected storage during image creation.
It’s quite confusing because this mean we could think that images are stored in the default storage whereas they are not and inversely.
Is it a bug or is this is a normal behaviour?
Does the storage setting in image creation has an influence or everything depends of location of the computer which deploy or capture?