On Wed, Nov 13, 2019 at 9:22 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:


Il giorno mar 12 nov 2019 alle ore 22:26 Nir Soffer <nsoffer@redhat.com> ha scritto:
We usually support only the most recent version of Fedora, which is now 31.

We can use Fedora 30 for a while, but it is really too old (older than
CentOS 8) and
there is on point to use it. Instead of helping to discover issues
early, we waste time
on dealing with old packages that nobody maintains.

For storage we need Fedora 31 for lvm 2.03, fixing critical issues.
Using Fedora 30, we will
have to add ugly hacks to have configuration that works with both versions.

For network we need newer versions of NetworkManager and initscripts
(Edward can add
more details).

For virt we use virt-preview repo, so we have recent versions of
libvirt and qemu on
any Fedora version (even 29).

I added Fedora 31 builds for imageio, and all tests pass in travis:
https://travis-ci.org/nirs/ovirt-imageio/builds/611042648

Adding ioprocess build should be easy, similar to this patch:
https://gerrit.ovirt.org/c/104634

On Jenkins the fc31 build fails since there is no mock env for Fedora 31:
https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-imageio_standard-check-patch/detail/ovirt-imageio_standard-check-patch/1628/pipeline/146

When do we plan to support Fedora 31?

Can you please open a ticket to infra to add mirroring for fedora 31 repos and mock config into jenkins?
Once both are ready we can switch to fedora 31.

Sendt mail to infra-support about this, we should have a ticket soon.
 

 

Nir



--