-
Bug
-
Resolution: Done
-
Major
-
Logging 6.2.0
-
False
-
-
False
-
NEW
-
NEW
-
Release Note Not Required
-
-
-
Log Collection - Sprint 267
-
Critical
Description of problem:
In some cases, the clf.status can not be displayed ( these status can be displayed in 6.1). I didn't gather all conditions. Just summary those cases I hit recently.
Cases 1: the CLF include an invalid secret key.
Expected result: status: conditions: outputConditions: - lastTransitionTime: "2025-02-25T13:34:31Z" message: secret[clf-71488.sharedkey.key ] not found reason: ValidationFailure status: "False" type: observability.openshift.io/ValidOutput-cloudwatch
Case 2: The pipelines using a not-existing filter(drop-logs here)
Expected result:
The clf.status show "Pipeline Condition invalid"
cases 3: the service account doesn't have enough permisison.
Expected result:
The clf.status show error 'insufficient permissions on service account, not authorized to collect ["infrastructure"] logs'
Case 4: the status can not be reported when the CLF is valid.
For example: we should see the full clf.status for the following CLF.
apiVersion: observability.openshift.io/v1 kind: ClusterLogForwarder metadata: creationTimestamp: "2025-02-26T06:33:30Z" generation: 1 name: collector namespace: test-clf resourceVersion: "142071" uid: 9ee014d9-a14f-492a-aaf2-b3cdf42cae1d spec: managementState: Managed outputs: - googleCloudLogging: authentication: credentials: key: google-application-credentials.json secretName: gcp-secret id: type: project value: openshift-gce-devel logId: app-gcp name: gcp-1 type: googleCloudLogging pipelines: - inputRefs: - application name: test-app outputRefs: - gcp-1 serviceAccount: name: logcollector
- links to
- mentioned on