Re: [ovirt-users] Failed to create template

2017-07-13 Thread Mike Farnam
Ok thanks. I'll try that today and report back if it made a difference or not. > On Jul 13, 2017, at 9:33 AM, Fred Rolland wrote: > > Yes. But the image should be uncompressed before you upload it. > >> On Jul 13, 2017 6:34 PM, "aduckers" wrote:

Re: [ovirt-users] Failed to create template

2017-07-13 Thread Fred Rolland
Yes. But the image should be uncompressed before you upload it. On Jul 13, 2017 6:34 PM, "aduckers" wrote: > Ok. I should be able to select QCOW2 for a SAN storage target? If true, > then I’ll need to figure out why that doesn’t work. > > On Jul 13, 2017, at 8:32 AM,

Re: [ovirt-users] Failed to create template

2017-07-13 Thread aduckers
Ok. I should be able to select QCOW2 for a SAN storage target? If true, then I’ll need to figure out why that doesn’t work. > On Jul 13, 2017, at 8:32 AM, Fred Rolland wrote: > > When you select RAW, the Vdsm will allocated the whole size of the image > (virtual size),

Re: [ovirt-users] Failed to create template

2017-07-13 Thread Fred Rolland
When you select RAW, the Vdsm will allocated the whole size of the image (virtual size), this is why you will not encounter this issue in Block Storage. On Thu, Jul 13, 2017 at 6:17 PM, aduckers wrote: > Thanks Fred. I haven’t run into the upload issue again, but if we

Re: [ovirt-users] Failed to create template

2017-07-13 Thread aduckers
Thanks Fred. I haven’t run into the upload issue again, but if we do I’ll try that. Regarding the template creation issue - could that just be user error on my part? I’ve found that if I select RAW format for the disk, when target is SAN, it works fine. QCOW2 format works for a target of

Re: [ovirt-users] Failed to create template

2017-07-13 Thread Fred Rolland
It seems you hit [1] If the image is compressed, the Vdsm will not compute the size as needed. In file storage, it will work OK as the file system is sparse. As a workaround you can decompress before uploading: qemu-img convert -f qcow2 rhel-guest-image-7.3-35.x86_64.qcow2 -O qcow2 -o compat=1.1

Re: [ovirt-users] Failed to create template

2017-07-05 Thread Fred Rolland
Can you please open bugs for the two issues for future tracking ? These needs further investigations. On Mon, Jul 3, 2017 at 2:17 AM, aduckers wrote: > Thanks for the assistance. Versions are: > > vdsm.x86_64 4.19.15-1.el7.centos > ovirt-engine.noarch

Re: [ovirt-users] Failed to create template

2017-07-02 Thread aduckers
Thanks for the assistance. Versions are: vdsm.x86_64 4.19.15-1.el7.centos ovirt-engine.noarch4.1.2.2-1.el7.centos Logs are attached. The GUI shows a creation date of 2017-06-23 11:30:13 for the disk image that is stuck finalizing, so that might be a good place to start in

Re: [ovirt-users] Failed to create template

2017-07-02 Thread Fred Rolland
Hi, Thanks for the logs. What exact version are you using ? (VDSM,engine) Regarding the upload issue, can you please provide imageio-proxy and imageio-daemon logs ? Issue in [1] looks with the same symptoms, but we need more info. Regarding the template issue, it looks like [2]. There were

Re: [ovirt-users] Failed to create template

2017-06-29 Thread Fred Rolland
Can you please attach engine and Vdsm logs ? On Thu, Jun 29, 2017 at 6:21 PM, aduckers wrote: > I’m running 4.1 with a hosted engine, using FC SAN storage. I’ve uploaded > a qcow2 image, then created a VM and attached that image. > When trying to create a template from

[ovirt-users] Failed to create template

2017-06-29 Thread aduckers
I’m running 4.1 with a hosted engine, using FC SAN storage. I’ve uploaded a qcow2 image, then created a VM and attached that image. When trying to create a template from that VM, we get failures with: failed: low level image copy failed VDSM command DeleteImageGroupVDS failed: Image does not