Is the intention of this clone to be backported to 3.5?
(In reply to Jeff Cantrill from comment #2) > Is the intention of this clone to be backported to 3.5? The issue is in the fluentd package (not in origin-aggregated-logging). Is some backporting effort still needed? (E.g., recreating an image?)
(In reply to Noriko Hosoi from comment #3) > (In reply to Jeff Cantrill from comment #2) > > Is the intention of this clone to be backported to 3.5? > > The issue is in the fluentd package (not in origin-aggregated-logging). Is > some backporting effort still needed? (E.g., recreating an image?) So we still need to get fluentd-0.12.39-2 for ocp 3.5, and build a fluentd image with that package?
(In reply to Jeff Cantrill from comment #2) > Is the intention of this clone to be backported to 3.5? Yes, we need this fix for 3.5, or any version where we turn on the use of "file" buffers.
File buffer was backported to 3.5, verified by QE and shipped. These are the bug and the errata advisory. - Bug 1477515 - [3.5] Data loss of logs can occur if fluentd pod is terminated/restarted when Elasticsearch is unavailable - https://access.redhat.com/errata/RHBA-2017:3049 According to the package list: https://access.redhat.com/downloads/content/290/ver=3.5/rhel---7/3.5.5.31.36/x86_64/packages the expected version of fluentd is included and shipped with ocp-3.5 (as well as ocp-3.4) https://access.redhat.com/downloads/content/rhel---7/x86_64/5801/fluentd/0.12.39-2.el7/noarch/fd431d51/package Since it's already released, changing the status CLOSED/CURRENTRELEASE.