fluent-bit: fluent-bit repo data not available for RHEL/CentOS/AlmaLinux/Rocky 9

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.

  • Steps to reproduce the problem: Either:
  • Run the setup script and note that it fails due to missing packages for the current version
  • Follow the manual steps in setting up a repo and note that it fails to install

Expected behavior The setup script and instructions successfully result in fluent-bit being installed for the current version of these supported distros.

Your Environment

  • Version used: fluent-bit-1.9.3-1.x86_64
  • Configuration: Native RPM install
  • Environment name and version (e.g. Kubernetes? What version?): Native RPM install
  • Server type and version: Linux
  • Operating System and version: CentOS Stream 9
  • Filters and plugins: n/a

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:

- name: Set fluentbit repo release version
  set_fact:
    fb_rel_ver: "{{ ansible_distribution_major_version }}"

- name: Set fluentbit repo release version (EL9)
  set_fact:
    fb_rel_ver: "8"
  when: ansible_distribution_major_version|int == 9

- name: Setup yum repo
  yum_repository:
    name: fluentbit
    description: Fluentbit Repo
    baseurl: "https://packages.fluentbit.io/centos/{{ fb_rel_ver }}/$basearch/"
    enabled: yes
    file: fluentbit
    gpgcheck: yes
    gpgkey: https://packages.fluentbit.io/fluentbit.key
    state: present

- name: Import rpm_key
  rpm_key:
    key: https://packages.fluentbit.io/fluentbit.key
    state: present

- name: Install fluentbit
  yum:
    name: fluent-bit
    state: latest

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (10 by maintainers)

Most upvoted comments

It already is, should have CentOS 9 repos available for new releases. Need to close this.

Great news @vwbusguy , obviously we tested as well but having an in the wild user confirm is super helpful!

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.

@vwbusguy the staging bucket should have CentOS 9 packages in it now: https://fluentbit-staging.s3.amazonaws.com/centos-9.repo

@vwbusguy not forgotten, this and Ubuntu 22 hopefully will be ready after the heatwave in Europe 👍

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.

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!

@vwbusguy could you submit a docs PR to cover the details for the installation page? https://github.com/fluent/fluent-bit-docs/blob/master/installation/linux/redhat-centos.md

Feel free to include your workaround if you can but the main thing to cover is to modify 9 --> 8. We can then update and remove this once we have 9 support official.