[libvirt-users] [BUG] Not exiting media forced a promptly close of libvirt 3.10

[Holger Schranz]

Sorry for an additional question:

In the bug report where Jim was wrote in his answer:
https://libvirt.org/git/?p=libvirt.git;a=commit;h=2d07f1f0ebd44b0348daa61afa0de34f3f838c22 

is a pointer to the report:
https://bugzilla.redhat.com/show_bug.cgi?id=1522682

In this report the fixed version is: libvirt-3.9.0-6.el7

How can I check/find whether this fix is include in the 3.10 which
I used?

Best regards

Holger

Am 23.12.2017 um 09:56 schrieb Holger Schranz:
> Hello,
>
> thanks for the information.
>
> Please let me ask: If understand correctly this issue occoured and 
> reported
> in 3.9? And the fix is for 3.11 or 4.0?
>
> Best regards
>
> Holger
>
> Am 22.12.2017 um 22:27 schrieb Jim Fehlig:
>> On 12/22/2017 02:21 AM, Holger Schranz wrote:
>>> Thread 1 (Thread 0x7f0d525ab700 (LWP 10729)):
>>> #0  virStorageFileReportBrokenChain (errcode=2, 
>>> src=src at entry=0x7f0d4004ac40, parent=0x7f0d4004ac40) at 
>>> storage/storage_source.c:422
>>>          access_user = <optimized out>
>>>          access_group = <optimized out>
>>>          __FUNCTION__ = "virStorageFileReportBrokenChain"
>>> #1  0x00007f0d4b56a262 in qemuDomainDetermineDiskChain 
>>> (driver=driver at entry=0x7f0d40240bf0, vm=vm at entry=0x7f0d400e66d0,
>>>      disk=disk at entry=0x7f0d4037fa80, 
>>> force_probe=force_probe at entry=true, 
>>> report_broken=report_broken at entry=true)
>>
>> This bug has already been fixed
>>
>> https://libvirt.org/git/?p=libvirt.git;a=commit;h=2d07f1f0ebd44b0348daa61afa0de34f3f838c22 
>>
>>
>> Regards,
>> Jim
>
>
> ---
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
> https://www.avast.com/antivirus
>
> _______________________________________________
> libvirt-users mailing list
> libvirt-users at redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-users