-
Bug
-
Resolution: Done
-
Normal
-
Logging 5.5.0
-
False
-
None
-
False
-
NEW
-
VERIFIED
-
Logging (Core) - Sprint 220, Log Collection - Sprint 221, Log Collection - Sprint 222
As per fix for LOG-2063, fluentd/vector only CL instance deployments should be stopped when CLF is missing. In the scenario where CLF is deleted, Collector DaemonSets are not removed/terminated.
CLF status:
status: clusterConditions: - lastTransitionTime: '2022-06-09T06:35:40Z' message: ClusterLogForwarder input validation error reason: ClusterLogForwarder input validation error status: 'True' type: CollectorDeadEnd - lastTransitionTime: '2022-06-09T06:30:38Z' message: curator is deprecated in favor of defining retention policy reason: ResourceDeprecated status: 'True' type: CuratorRemoved
$ oc get daemonsets -n openshift-logging NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE collector 6 6 6 6 6 kubernetes.io/os=linux 8m41s
$ oc get pods | grep collector collector-6zwjt 2/2 Running 0 8m54s collector-8rcds 2/2 Running 0 8m44s collector-8t5lc 2/2 Running 0 8m29s collector-jzndm 2/2 Running 0 8m38s collector-kzrm5 2/2 Running 0 8m49s collector-pwvsx 2/2 Running 0 8m34s
CSV version: cluster-logging.5.5.0
How reproducible: Always
Steps to reproduce:
1) Deploy Logging Operators
2) Create CLF to forward logs to external logstore
3) Provision fluentd/vector only CL instance
4) Remove the CLF after collector pods are running
Expected Result:
Collector deployment should be stopped.
Actual Result:
Collector pods are still running.
