-
Bug
-
Resolution: Done
-
Critical
-
Logging 5.7.0
-
False
-
None
-
False
-
NEW
-
NEW
-
-
-
Log Collection - Sprint 233, Log Collection - Sprint 234
Description of problem:
When clusterlogging are deployed using deprecated format(spec.collection.type is not defined). the clusterlogging instance cat not be upgraded from 5.6 to 5.7.0
Steps to Reproduce:
- Deploy clusterlogging without spec.collection.type.
apiVersion: logging.openshift.io/v1
kind: ClusterLogging
metadata:
name: instance
namespace: openshift-logging
spec:
collection:
logs:
fluentd: {}
type: fluentd
managementState: Managed
logStore:
....
2. Upgrade clusterlogging to 5.7.0
Actual results:
Clusterlogging can not be upgraded to 5.7.0
$ oc get csv
NAME DISPLAY VERSION REPLACES PHASE
cluster-logging.v5.6.4 Red Hat OpenShift Logging 5.6.4 cluster-logging.v5.6.3 Replacing
cluster-logging.v5.7.0 Red Hat OpenShift Logging 5.7.0 cluster-logging.v5.6.4 Pending
$oc get ip install-c2clt -o json |jq '.status.conditions'
[
{ "lastTransitionTime": "2023-03-17T01:55:04Z", "lastUpdateTime": "2023-03-17T01:55:04Z", "message": "error validating existing CRs against new CRD's schema for \"clusterloggings.logging.openshift.io\": error validating custom resource against new schema for ClusterLogging openshift-logging/instance: [].spec.collection.type: Required value", "reason": "InstallComponentFailed", "status": "False", "type": "Installed" }
]
Expected results:
Add this issue as knonw issue. Or allow clusterlogging to be upgraded when spec.collection.type is not defined.
Additional info:
Workaround
1) delete sub/cluster-logging, csv/clusterlogging.
2) upgrade clusterlogging/instance to use spec.collection.type
3) subscribe to clusterlogging 5.7.0 directly
- links to
- mentioned on
[LOG-3809] The CLO can not be upgraded when spec.collection.type is not defined
GitLab CEE Bot
added a comment - CPaaS Service Account mentioned this issue in a merge request of openshift-logging / Log Collection Midstream on branch openshift-logging-5.7-rhel-8_upstream_839275f65c89aefbece63343e3dd8dd2:
Updated US source to: 718a8c8 Merge pull request #1933 from jcantrill/log3824
GitLab CEE Bot
added a comment - CPaaS Service Account mentioned this issue in a merge request of openshift-logging / Log Collection Midstream on branch openshift-logging-5.7-rhel-8_ upstream _839275f65c89aefbece63343e3dd8dd2 : Updated US source to: 718a8c8 Merge pull request #1933 from jcantrill/log3824 GitLab CEE Bot
added a comment - CPaaS Service Account mentioned this issue in a merge request of openshift-logging / Log Collection Midstream on branch openshift-logging-5.7-rhel-8_upstream_ff3045f9668698118eb9a284025b3247:
Updated US source to: 1a4f753 Merge pull request #1923 from jcantrill/log3809
GitLab CEE Bot
added a comment - CPaaS Service Account mentioned this issue in a merge request of openshift-logging / Log Collection Midstream on branch openshift-logging-5.7-rhel-8_ upstream _ff3045f9668698118eb9a284025b3247 : Updated US source to: 1a4f753 Merge pull request #1923 from jcantrill/log3809 
Verified on openshift-logging/cluster-logging-rhel8-operator/images/v5.7.0-80. cluster-logging.v5.6.4 can be upgraded to cluster-logging.v5.7.0 when collection.logs.type is defined.
The clusterlogging/instance updated as below
5.6.5
spec: collection: logs: type: vector5.7.0
spec: collection: logs: type: vector type: vector