Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-2775

Port LOG-2635 fix into CLO 5.4

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Critical
    • None
    • None
    • Log Collection
    • None
    • False
    • None
    • False
    • NEW
    • NEW

    Description

      LOG-2635 was initially created for a bug related to CLO filling tmfs and causing control plane instability due memory exhaustion. This has been since resolved and fix has been added to CLO 5.2.z

      This card is to port that fix into CLO (cluster logging operator) 5.4.z so that customers that have installed the operator from OperatorHub can also receive the fix in LOG-2635.

      Currently, This is affecting 9 managed openshift clusters where SRE is performing manual workaround each time (almost every day) a cluster experiences control plane degradation due to this issue.

      Acceptance Criteria:

      • LOG-2635 fix is ported into CLO 5.4.z and an update to the fixed version is available on OperatorHub 

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. LOG-2635 CloudWatch forwarding rejecting large log events, fills tmpfs

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              Unassigned Unassigned
              kramraja.openshift Karthik Perumal
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: