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 <froll...@redhat.com> wrote: > > 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 <alex.duck...@gmail.com > <mailto:alex.duck...@gmail.com>> wrote: > 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 NFS. > Is that the way it’s supposed to behave? > > >> On Jul 13, 2017, at 7:59 AM, Fred Rolland <froll...@redhat.com >> <mailto:froll...@redhat.com>> wrote: >> >> 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 uncompressed.qcow2 >> >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1470435 >> <https://bugzilla.redhat.com/show_bug.cgi?id=1470435> >> >> On Wed, Jul 5, 2017 at 10:44 AM, Fred Rolland <froll...@redhat.com >> <mailto:froll...@redhat.com>> wrote: >> 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 <alex.duck...@gmail.com >> <mailto:alex.duck...@gmail.com>> wrote: >> Thanks for the assistance. Versions are: >> >> vdsm.x86_64 4.19.15-1.el7.centos >> ovirt-engine.noarch 4.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 the logs. >> >> >> >> >> >> > On Jul 2, 2017, at 3:52 AM, Fred Rolland <froll...@redhat.com >> > <mailto:froll...@redhat.com>> wrote: >> > >> > 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 some issues when calculating the estimated size target volume, >> > that should be already fixed. >> > Please provide the exact versions, so I can check if it includes the fixes. >> > >> > Thanks, >> > >> > Fred >> > >> > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1357269 >> > <https://bugzilla.redhat.com/show_bug.cgi?id=1357269> >> > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1448606 >> > <https://bugzilla.redhat.com/show_bug.cgi?id=1448606> >> > >> > >> > On Fri, Jun 30, 2017 at 5:11 AM, aduckers <alex.duck...@gmail.com >> > <mailto:alex.duck...@gmail.com>> wrote: >> > >> > >> > Attached. I’ve also got an image upload to the ISO domain stuck in >> > “Finalizing”, and can’t cancel or clear it. Not sure if related or not, >> > but it might show in the logs and if that can be cleared that’d be great >> > too. >> > >> > Thanks >> > >> > >> >> On Jun 29, 2017, at 9:20 AM, Fred Rolland <froll...@redhat.com >> >> <mailto:froll...@redhat.com>> wrote: >> >> >> >> Can you please attach engine and Vdsm logs ? >> >> >> >> On Thu, Jun 29, 2017 at 6:21 PM, aduckers <alex.duck...@gmail.com >> >> <mailto:alex.duck...@gmail.com>> 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 that VM, we get failures with: >> >> >> >> failed: low level image copy failed >> >> VDSM command DeleteImageGroupVDS failed: Image does not exist in domain >> >> failed to create template >> >> >> >> What should I be looking at to resolve this? Anyone recognize this issue? >> >> >> >> Thanks >> >> >> >> >> >> _______________________________________________ >> >> Users mailing list >> >> Users@ovirt.org <mailto:Users@ovirt.org> >> >> http://lists.ovirt.org/mailman/listinfo/users >> >> <http://lists.ovirt.org/mailman/listinfo/users> >> >> >> > >> > >> > >> >> >> >> > >
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
