-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fluent-bit repo data not available for RHEL/CentOS/AlmaLinux/Rocky 9 #5478
Comments
RHEL 9 targets are not officially supported yet (and it is only just GA): https://docs.fluentbit.io/manual/installation/supported-platforms. There are other requests for this so it will be done "soon" although a PR to provide the support will be massively helpful. This will be on the backlog and done as soon as possible but a PR will speed that up. cc @niedbalski |
@vwbusguy could you submit a docs PR to cover the details for the installation page? Feel free to include your workaround if you can but the main thing to cover is to modify 9 --> 8. |
For reference, the main changes required are:
If we get #5098 sorted then we "only" need to concern ourselves with build changes and updates to the packaging scripts that create the repos. Otherwise we also have some release infrastructure set up to cope with too then the sync over to it. |
For what it's worth, we are running a mix of Alma, CentOS Stream, and RHEL and are using a common playbook for all of them from EL7-9 and everything seems to be happy so far (except for pointing EL9 stuff to 8). Targeting Stream for CI environments has been generally useful for us, since we find out sooner about changes that will impact Alma/RHEL, etc. sooner. The fact that EL8 packages work in CentOS Stream 9 is a good sign that it will probably work fine regardless of which flavor you pick :-). That said, I'll try to get a PR for you for the docs page. Thanks! |
OK cool, good to know - although I'm still not convinced it won't deviate significantly as time marches on! 👍 KISS though would be to go with the combined target until it breaks for the others. |
@vwbusguy not forgotten, this and Ubuntu 22 hopefully will be ready after the heatwave in Europe 👍 |
Ubuntu 22 is up now thankfully, I think this will likely have to wait for FB 2.0 unfortunately |
@vwbusguy would you be able to test some preliminary packages across your various types of "RHEL 9 compatible" targets? |
Sure. I can do that on Monday (assuming I remember to check back here then). |
@vwbusguy the staging bucket should have CentOS 9 packages in it now: https://fluentbit-staging.s3.amazonaws.com/centos-9.repo |
My apologies - it appears that I did not, in fact, remember to check back. If I get a moment today, I'll update update our playbook and try it against one of our EL9 hosts with that repo. |
I had a spare moment and updated the playbook to point to that repo for EL9 hosts and it works! Tested the playbook out against an AlmaLinux 9 node and it's up and running:
|
Great news @vwbusguy , obviously we tested as well but having an in the wild user confirm is super helpful! |
Is there any update on status of when this will be ready for stable/prod repos? |
It already is, should have CentOS 9 repos available for new releases. Need to close this. |
Bug Report
Describe the bug
While the el8 package appears to work on el9 for now, the default repo config will reference version 9 in the repo URL which doesn't exist. Adding packages to support the current version of these distributions will make improve the experience of installing fluent-bit.
To Reproduce
Attempt to follow any install instructions from https://docs.fluentbit.io/manual/installation/linux/redhat-centos using any EL9 distribution.
Either:
Expected behavior
The setup script and instructions successfully result in fluent-bit being installed for the current version of these supported distros.
Your Environment
Additional context
For now we've implemented a hacky workaround in Ansible to attempt to identify an EL9 box and override the yum repo to point to the EL8 repos. The package installs fine for now, but it definitely added to the complexity of adopting fluent-bit to our environment.
Here's our current Ansible workaround in case others are similarly affected by this:
The text was updated successfully, but these errors were encountered: