On Fri, Mar 13, 2020 at 14:15:25 +0100, Peter Krempa wrote:
On Fri, Mar 13, 2020 at 14:05:54 +0100, Kashyap Chamarthy wrote:
On Fri, Mar 13, 2020 at 01:08:47PM +0100, Peter Krempa wrote:
On Wed, Mar 11, 2020 at 11:09:40 -0500, Eric Blake wrote:
[...]
I'm not sure about the value of exposing this particular situation since it's a regression of behaviour which is being rectified. The code driving it in oVirt will stay the same and the only thing that could be changed is the error message reported. oVirt probably wants just blacklist the 3 releases that are broken.
Just for the record, can you please note the three affected libvirt releases? (It'll help us refer to your response when answering users/admins at a future time.)
It affects libvirt-5.10, libvirt-6.0 and libvirt-6.1.
Also should this be documented elsewhere?
I can add a news.xml entry
https://www.redhat.com/archives/libvir-list/2020-March/msg00496.html