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

Delete the logforwarding CR, but still the collector pods are up and running

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Before this update, when no logstore has been specified, the collector daemonset was not being removed when clusterlogforwarder instance was deleted. With this update, the daemonset is removed as expected.
    • Bug Fix
    • Done
    • Log Collection - Sprint 235, Log Collection - Sprint 236

      Description of problem:

      Why collector pod is not starting for the first time and started only when logforwarding is configured ? And why not same behaviour after deleting the logforwarder ?

      Version-Release number of selected component (if applicable):

      cluster-logging.v5.6.3
      OCPv4.12.13

      How reproducible:

      1.  Configured cluster logging CR.
      2. Collector pods is not created. 3. Once we configure logforwarding CR, collector pods are started.
      3. Delete the logforwarding CR, still the collector pods are up and running
      4. Delete the collector pod, it gets recreated automatically (Even though logforwarding is not configured)

      Steps to Reproduce:

      1.  
      2.  
      3. ...

      Actual results:

      Expected results:

      Additional info:

      Slack thread: https://redhat-internal.slack.com/archives/CB3HXM2QK/p1683026867437779

        1. clo_pod_logs.txt
          892 kB
        2. collector_pod_logs.txt
          9 kB
        3. logfilesmetricexporter_logs.txt
          0.1 kB
        4. logging-manifest.tar.gz
          0.8 kB
        5. operations_console_logs.txt
          7 kB

              cahartma@redhat.com Casey Hartman
              midu@redhat.com Mihai IDU
              Kabir Bharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: