-
Bug
-
Resolution: Done
-
Blocker
-
Logging 5.5.4
-
False
-
None
-
False
-
NEW
-
VERIFIED
-
Before this update a prior refactoring of the logging `must-gather` scripts removed the expected location for the artifacts. This update reverts that change to write artifacts to the `/must-gather` folder.
-
Log Collection - Sprint 227
'oc adm must-gather' is resulting in empty folder for logging with CLO image.
Logging version: 5.5.3(4)
Cluster version: 4.11
Below is the output for must-gather:
$ oc adm must-gather --image=$(oc -n openshift-logging get deployment.apps/cluster-logging-operator -o jsonpath='
') – /usr/bin/gather
[must-gather ] OUT Using must-gather plug-in image: registry.redhat.io/openshift-logging/cluster-logging-rhel8-operator@sha256:1541dd27c871c9744053fc5552a96211602d5511df1e53447f20bc0281709359 When opening a support case, bugzilla, or issue please include the following summary data along with any other requested information: ClusterID: 3888fb0a-9062-4624-ab8c-952d00722414 ClusterVersion: Stable at "4.11.0-0.nightly-2022-10-19-130222" ClusterOperators: All healthy and stable [must-gather ] OUT namespace/openshift-must-gather-8cpcs created [must-gather ] OUT clusterrolebinding.rbac.authorization.k8s.io/must-gather-scjxl created [must-gather ] OUT pod for plug-in image registry.redhat.io/openshift-logging/cluster-logging-rhel8-operator@sha256:1541dd27c871c9744053fc5552a96211602d5511df1e53447f20bc0281709359 created [must-gather-cpjw7] OUT waiting for gather to complete [must-gather-cpjw7] OUT downloading gather output [must-gather-cpjw7] OUT receiving incremental file list [must-gather-cpjw7] OUT ./ [must-gather-cpjw7] OUT [must-gather-cpjw7] OUT sent 27 bytes received 40 bytes 12.18 bytes/sec [must-gather-cpjw7] OUT total size is 0 speedup is 0.00 [must-gather ] OUT namespace/openshift-must-gather-8cpcs deleted [must-gather ] OUT clusterrolebinding.rbac.authorization.k8s.io/must-gather-scjxl deleted Reprinting Cluster State: When opening a support case, bugzilla, or issue please include the following summary data along with any other requested information: ClusterID: 3888fb0a-9062-4624-ab8c-952d00722414 ClusterVersion: Stable at "4.11.0-0.nightly-2022-10-19-130222" ClusterOperators: All healthy and stable
