The fluentd images we ship depend on the Ruby from RHEL which is apparently 2.0.0-p648. That version appears to be EOL: https://www.ruby-lang.org/en/news/2016/02/24/support-plan-of-ruby-2-0-0-and-2-1/ We should consider what it takes to move the logging images to a version that is not EOL. There are other products, e.g. CloudForms, which are using versions of Ruby that are not EOL (2.2 and 2.3, currently, looking to drop 2.2 when 2.4 support is announced).
We are going to have to switch to using ruby 2.3 or later from SCL when we move to fluentd 0.14. In the meantime, I trust that the RHEL/ruby team will be supporting not only us by all of the other products, projects, and customers that are using the ruby provided by RHEL.
Can we discuss this more?
Recently heard that Rich build a fluentd image use s2i using Ruby 2.3. I think Anton also was able to do the same thing.
This isn't an s2i image - it's the centos-ruby-24 base image.
3.10 at the earliest. We are going to have to port all 90+ rubygem packages to be SCL enabled.
--- Comment #2 from Vít Ondruch <vondruch> --- Ruby 2.0 being part of RHEL7 is supported under the same conditions as RHEL7: https://access.redhat.com/support/policy/updates/errata/
OCP 4.0 uses Fluentd 1.x running on a ruby 2.5 SCL image.
Move to verified as comment 12
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758