-
Bug
-
Resolution: Done-Errata
-
Minor
-
Logging 5.8.z, Logging 5.9.z
-
False
-
None
-
False
-
NEW
-
VERIFIED
-
-
-
Log Collection - Sprint 255
-
Moderate
Description of problem:
If you previously used the "spec.collection.logs.*" notation and then changed to the new "spec.collection.*" notation, you still see Deprecated=True as follows:
$ oc get clusterlogging instance -n openshift-logging -oyaml
apiVersion: logging.openshift.io/v1
kind: ClusterLogging
metadata:
creationTimestamp: "2024-05-31T02:11:20Z"
generation: 2
name: instance
namespace: openshift-logging
resourceVersion: "44751"
uid: 59cb70e6-48d3-45a9-a09e-4a05e5f8809b
spec:
collection:
type: vector
status:
conditions:
- lastTransitionTime: "2024-05-31T02:11:20Z"
message: spec.collection.logs.* is deprecated in favor of spec.collection.*
reason: DeprecatedCollectionLogsSpec
status: "True"
type: Deprecated
logStore: {}
visualization: {}
This confuses customers who have migrated from fluentd to vector about whether something is written wrong.
Version-Release number of selected component (if applicable):
OpenShift Logging 5.9, 5.8
How reproducible:
100%
Steps to Reproduce:
1. Install OpenShift Logging Operator:
2. Run the following command
oc apply -f - <<EOF
apiVersion: logging.openshift.io/v1
kind: ClusterLogging
metadata:
name: instance
namespace: openshift-logging
spec:
collection:
logs:
type: vector
EOF
3. Run "oc edit ClusterLogging instance -n openshift-logging" and edit as follows:
(before)
collection:
logs:
type: vector
(after)
collection:
type: vector
4. Run "oc get clusterlogging instance -n openshift-logging -oyaml" and you still see the Deprecated message
Actual results:
Deprecated message appears despite writing correctly
Expected results:
No Deprecated message
Additional info:
- links to
-
RHSA-2024:4333
security update Logging for Red Hat OpenShift - 5.9.4
- mentioned on
