-
Bug
-
Resolution: Done
-
Normal
-
Logging 5.1
-
False
-
False
-
NEW
-
VERIFIED
-
Before this update, <X problem> caused <Y situation> (OPTIONAL: under the following <Z conditions>). With this update, <fix> resolves the issue (OPTIONAL: and <agent> can <perform operation> successfully).
Description of problem:
Deploy logging, then run `oc adm must-gather --image=$(oc -n openshift-logging get deployment.apps/cluster-logging-operator -o jsonpath='{.spec.template.spec.containers[?(@.name == "cluster-logging-operator")].image}') ` to gather logging information, check the gathered files, the csv under `must-gather.local.1681620295046205588/$image-name/cluster-logging/clo/` is empty:
$ ls csv -l -rw-r--r--. 1 qitang qitang 0 Jul 1 21:36 csv
I checked https://github.com/openshift/cluster-logging-operator/blob/release-5.1/must-gather/collection-scripts/gather_cluster_logging_operator_resources#L29-L30, when deploy CLO with downstream images, the CSV name is `cluster-logging.5.1.0-54` not `cluster-logging-operator.xxxxx`
Besides, the events are not collected in *-events.yaml, look like the content in these files is an error message:
$ cat clo-events.yaml flags cannot be placed before plugin name: -n $ cat clf-events.yaml flags cannot be placed before plugin name: -n
I find there are 2 `oc` in one command: https://github.com/openshift/cluster-logging-operator/blob/release-5.1/must-gather/collection-scripts/gather_cluster_logging_operator_resources#L45-L46
Version-Release number of selected component (if applicable):
cluster-logging.5.1.0-54
How reproducible:
Always
Steps to Reproduce:
1. deploy logging
2. run `oc adm must-gather` with downstream CLO image
3. check the files gathers in step 2
Actual results:
Expected results:
Additional info:
- clones
-
LOG-2761 [release-5.3]Events and CLO csv are not collected after running `oc adm must-gather --image=$downstream-clo-image `
- Closed
- links to