libvirt users - Mar 2016 - Buggy 1.3.2? Disconnected from qemu:///session due to I/O error

I think I've hit the same problem that Predrag reported in
http://comments.gmane.org/gmane.comp.emulators.libvirt.user/8825.

With libvirt-1.3.2-1.fc23.x86_64 on Fedora 23, when I try uploading an
image with vol-upload to a user libvirtd (qemu:///session):

    virsh vol-upload --pool default volume.qcow /path/to/file.qcow2

I am getting:

    error: Disconnected from qemu:///session due to I/O error
    error: cannot send data to volume volume.qcow2
    error: Cannot write data: Broken pipe

    error: One or more references were leaked after disconnect from the
hypervisor

If I downgrade to libvirt-1.2.18.2-2.fc23.x86_64 (which is what
actually ships in F23), the image upload completes without a problem.

-- 
Lars Kellogg-Stedman <lars@redhat.com> | larsks @
{freenode,twitter,github}
Cloud Engineering / OpenStack          | http://blog.oddbit.com/

On Wed, Mar 09, 2016 at 10:18:10PM -0500, Lars Kellogg-Stedman
wrote:
> I think I've hit the same problem that Predrag reported in
> http://comments.gmane.org/gmane.comp.emulators.libvirt.user/8825.
> 
> With libvirt-1.3.2-1.fc23.x86_64 on Fedora 23, when I try uploading an
> image with vol-upload to a user libvirtd (qemu:///session):
> 
>     virsh vol-upload --pool default volume.qcow /path/to/file.qcow2
> 
> I am getting:
> 
>     error: Disconnected from qemu:///session due to I/O error
>     error: cannot send data to volume volume.qcow2
>     error: Cannot write data: Broken pipe
> 
>     error: One or more references were leaked after disconnect from the
hypervisor
> 
> If I downgrade to libvirt-1.2.18.2-2.fc23.x86_64 (which is what
> actually ships in F23), the image upload completes without a problem.
 
Yes, it's a known bug (and is fixed upstream):

    https://bugzilla.redhat.com/show_bug.cgi?id=1315606

Rich W.M. Jones informed on IRC a little while ago that the fix for the
above bug is included in the current libvirt packages in F24/Rawhide.

I've just installed it, and it fixes the bug for me:

    $ rpm -q libvirt
    libvirt-1.3.2-2.fc25.x86_64

    $ rpm -q libvirt --changelog | head -2
    * Wed Mar 09 2016 Richard W.M. Jones <rjones@redhat.com> - 1.3.2-2
    - Add fix for RHBZ#1315606.

-- 
/kashyap