Fedora 28 will be EOL in few month, and at this point people are migration to Fedora 29. I tried yesterday to build engine development setup on Fedora 29 VM, and found that it does not work: - some packages are missing on engine side - after hacking the ovirt.repo files, pointing to "28" instead of "$releasever", I got the packages... - but then adding a host fail with "Python is missing" on the host, which is working Fedora 28 host used with engine before. What are our plans for supporting Fedora 29 on engine and host? I hope that the work we did for Fedora 28 will make it easier to port to Fedora 29.

Nir

Il giorno lun 1 apr 2019 alle ore 16:04 Nir Soffer <nsoffer(a)redhat.com&gt; ha scritto: > Fedora 28 will be EOL in few month, and at this point people are > migration to Fedora 29. > > I tried yesterday to build engine development setup on Fedora 29 VM, and > found that it does > not work: > - some packages are missing on engine side > - after hacking the ovirt.repo files, pointing to "28" instead of > "$releasever", I got the packages... > - but then adding a host fail with "Python is missing" on the host, which > is working Fedora 28 host > used with engine before. > > What are our plans for supporting Fedora 29 on engine and host? > > I hope that the work we did for Fedora 28 will make it easier to port to > Fedora 29. > I would rather target Fedora 30 which should be available 1 month before Fedora 28 EOL. What do you think?

On Mon, Apr 1, 2019 at 6:07 PM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; wrote: > > > Il giorno lun 1 apr 2019 alle ore 16:04 Nir Soffer <nsoffer(a)redhat.com&gt; > ha scritto: > >> Fedora 28 will be EOL in few month, and at this point people are >> migration to Fedora 29. >> >> I tried yesterday to build engine development setup on Fedora 29 VM, and >> found that it does >> not work: >> - some packages are missing on engine side >> - after hacking the ovirt.repo files, pointing to "28" instead of >> "$releasever", I got the packages... >> - but then adding a host fail with "Python is missing" on the host, >> which is working Fedora 28 host >> used with engine before. >> >> What are our plans for supporting Fedora 29 on engine and host? >> >> I hope that the work we did for Fedora 28 will make it easier to port to >> Fedora 29. >> > > I would rather target Fedora 30 which should be available 1 month before > Fedora 28 EOL. > What do you think? > This could if Fedora 30 was not removing python 2 packages, but without python 2 packages we cannot use Fedora 30 to develop 4.4. We will have to use either Fedora 28 or 29 while we port vdsm to python 3. Only when all the code is ported and tested, somewhere near the end of the 4.4 development cycle, we can drop python 2 code. For engine developers not supporting Fedora 29 means that you cannot run engine on your laptop, which is the way most people work. Nir