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

[5.6] Collector restarts after creation

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Hide
      Before this change, once logging is deployed, and collector pod gets created, collector pod will restart once after one or two minutes.
      After this change, once logging is deployed collector does not restart on its own.
      Show
      Before this change, once logging is deployed, and collector pod gets created, collector pod will restart once after one or two minutes. After this change, once logging is deployed collector does not restart on its own.
    • Log Collection - Sprint 231, Log Collection - Sprint 232

      Description of problem:

      After deploying Log Forwarder, collector pod gets created, but after some time Collector pod gets restarted.

      It is observed that collector gets restarted once trusted ca-bundle config map gets created.

      On CRC cluster, SCC adds "hostPath" volume to the SCC, which is not present in the desired set of SCC volume.

      This behavior is independent of collector type.

       

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

      How reproducible:

      Always

      Steps to Reproduce:

      1. Deploy Logging
      2. Deploy CLF
      3. ...

      Actual results:

      Collector gets restarted

      Expected results:

      Collector should not get restarted

      Additional info:

              vimalkum@redhat.com Vimal Kumar
              vimalkum@redhat.com Vimal Kumar
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: