On Fri, Feb 27, 2015 at 03:48:22PM -0500, Nir Soffer wrote:
----- Original Message -----
From: "Nir Soffer" <nsoffer@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: announce@ovirt.org, Users@ovirt.org, devel@ovirt.org Sent: Friday, February 27, 2015 10:35:52 PM Subject: Re: [ovirt-users] [ovirt-devel] [ANN] oVirt 3.5.2 First Release Candidate is now available for testing
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: announce@ovirt.org, devel@ovirt.org, Users@ovirt.org Sent: Friday, February 27, 2015 12:00:10 PM Subject: [ovirt-devel] [ANN] oVirt 3.5.2 First Release Candidate is now available for testing
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The oVirt team is pleased to announce that the 3.5.2 First Release Candidate is now available for testing as of Feb 27th 2015.
The release candidate is available now for Fedora 20...
Do we support Fedora 21?
I don't recall a formal statement about it, but I surely WANT to support it, as nowadays it is the run-of-the-mill Fedora version.
May be also relevant for Fedora 20 with virt-preview repository.
Note also that we cannot use libvirt 1.2.8 on Fedora 20, since it contains critical bug that breaks live storage migration. This bug was fixed in libvirt 1.2.9. See https://bugzilla.redhat.com/1176673
Summary: - Fedora 20 is ok since it uses libvirt 1.1.3. - Fefora 20 with virt-preview must provide libvirt >= 1.2.9 and vdsm must include the patch bellow - Fedora 21 provides libvirt 1.2.9 and vdsm must include the patch bellow.
These requirement are not enforced in vdsm spec yet.
If we do, then this fix _must_ be included in 3.5.2: https://gerrit.ovirt.org/38201 vm: Fix LSM when using libvirt >= 1.2.8
Please mark the relevant bug as a blocker of the 3.5.2 tracker. That would make sure we don't release without it.