Releases for EOL Fedora, why ?

Development
1

Hi,

Why are the latest Fedora versions so poorly supported and EOL ones are ?

Because of this there is a very annoying gap for freeIPA releases as CentOS
is too far behind on FreeIPA and Foreman doesn't support the proxy on the
latest supported Fedora version.

Any idea how to fix this annoying gap all the time ?

Thanks,

Matt

2

Why are the latest Fedora versions so poorly supported and EOL ones are ?

Lack of time to properly package and test it. Is the primairy reason. Another thing that was always difficult for the main foreman package was keeping rails versions aligned.

Somewhere we decided to drop F24 but not add a newer Fedora release. Now that core is upgrading to Rails 5.1 we could target F27 again.

Because of this there is a very annoying gap for freeIPA releases as CentOS
is too far behind on FreeIPA and Foreman doesn't support the proxy on the
latest supported Fedora version.

The proxy should be much easier to support since it has fewer dependencies. The hardest part might be that our current testing is based on booting a Foreman instance with a proxy and see if it registers. If we boot a proxy but not a Foreman we'll need new tests so it's sufficiently covered.

We do have pipelines in forklift[1] that deploy a separate proxy - that could be modified to test the proxy on Fedora but deploy foreman on CentOS. Biggest worry there is CI resources but we're working on that.

Any idea how to fix this annoying gap all the time ?

Help us fix it in the foreman-packaging[2] repository. I'd be happy to help you in getting things going.

[1]: https://github.com/theforeman/forklift
[2]: https://github.com/theforeman/foreman-packaging

···

On Sun, Dec 17, 2017 at 02:11:25AM -0800, Matt wrote:

3

Hi Ewoud,

I would love to help but I need to find out more about that when I have
time for it. It's not something you want to figure out in a day.

In my case I was actually only talking about the proxy, but you are right
there is more then the proxy only but the proxy itself is creating the gap
here on Fedora.

For now I have created a CentOS "ProxyBox" that will be running a supported
version of the proxy and FreeIPA where CentOS is still a little bit behind.
At least my core machines are not affected when I have a problem with my
proxy.

I hope I'm able to help you out here or that the devs are able to focus for
the proxy at least more on latest Fedora versions.

···

Op zondag 17 december 2017 13:52:51 UTC+1 schreef Ewoud Kohl van Wijngaarden:

On Sun, Dec 17, 2017 at 02:11:25AM -0800, Matt wrote:
>Why are the latest Fedora versions so poorly supported and EOL ones are ?

Lack of time to properly package and test it. Is the primairy reason.
Another thing that was always difficult for the main foreman package was
keeping rails versions aligned.

Somewhere we decided to drop F24 but not add a newer Fedora release. Now
that core is upgrading to Rails 5.1 we could target F27 again.

>Because of this there is a very annoying gap for freeIPA releases as
CentOS
>is too far behind on FreeIPA and Foreman doesn't support the proxy on the
>latest supported Fedora version.

The proxy should be much easier to support since it has fewer
dependencies. The hardest part might be that our current testing is
based on booting a Foreman instance with a proxy and see if it
registers. If we boot a proxy but not a Foreman we'll need new tests so
it's sufficiently covered.

We do have pipelines in forklift[1] that deploy a separate proxy - that
could be modified to test the proxy on Fedora but deploy foreman on
CentOS. Biggest worry there is CI resources but we're working on that.

>Any idea how to fix this annoying gap all the time ?

Help us fix it in the foreman-packaging[2] repository. I'd be happy to
help you in getting things going.

[1]: https://github.com/theforeman/forklift
[2]: https://github.com/theforeman/foreman-packaging