-
Bug
-
Resolution: Done
-
Undefined
-
Logging 5.6.0
-
False
-
None
-
False
-
NEW
-
VERIFIED
-
-
-
-
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:
- Deploy Logging
- Deploy CLF
- ...
Actual results:
Collector gets restarted
Expected results:
Collector should not get restarted
Additional info:
[LOG-3608] [5.6] Collector restarts after creation
Verified on registry.redhat.io/openshift-logging/cluster-logging-rhel8-operator@sha256:1b73b8235925fc895168b52a77ebcf10e0133fd69871213d2c0fc17a4684305a
Collector pods are not restarting anymore.
$ oc get clusterlogforwarder -n openshift-logging
NAME AGE
instance 34m
$ oc get pods -n openshift-logging
NAME READY STATUS RESTARTS AGE
cluster-logging-operator-847cb56874-mlrmt 1/1 Running 0 36m
collector-774fv 2/2 Running 0 33m
collector-d4m6b 2/2 Running 0 33m
collector-mh2kh 2/2 Running 0 33m
collector-nmgth 2/2 Running 0 33m
collector-sq8r7 2/2 Running 0 33m
collector-wghjt 2/2 Running 0 33m
elasticsearch-cdm-orj32m2a-1-75f7c68c89-95wjz 2/2 Running 0 33m
elasticsearch-cdm-orj32m2a-2-6cc4b65ffb-vgb8z 2/2 Running 0 33m
elasticsearch-cdm-orj32m2a-3-67d5b8f48c-2tbdw 2/2 Running 0 33m
elasticsearch-im-app-27941385-bnfln 0/1 Completed 0 11m
elasticsearch-im-audit-27941385-rxm6j 0/1 Completed 0 11m
elasticsearch-im-infra-27941385-q99rs 0/1 Completed 0 11m
kibana-5dcc46b495-vxcmj 2/2 Running 0 33m
GitLab CEE Bot
added a comment - CPaaS Service Account mentioned this issue in merge request !862 of openshift-logging / Log Collection Midstream on branch openshift-logging-5.6-rhel-8_upstream_f2ddbaf0c83f6b0112f6c6ff4ee2abef:
Updated 2 upstream sources
GitLab CEE Bot
added a comment - CPaaS Service Account mentioned this issue in merge request !862 of openshift-logging / Log Collection Midstream on branch openshift-logging-5.6-rhel-8_ upstream _f2ddbaf0c83f6b0112f6c6ff4ee2abef : Updated 2 upstream sources
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Logging Subsystem 5.6.2 - Red Hat OpenShift), 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-2023:0793