Currently oc adm must-gather prints all log lines together, but we need a prefix to tell which is coming from stdout and which from stderr.
More precisely, we need to know which lines come from the pod we're running and which lines are from the command itself. We're getting bugs about output from other product's gather scripts.
Confirmed with latest oc version: 4.2.0-201909041019.git.1.c97b1af.el7 the stdout and stderr prefixed like this : [must-gather-np8xr] POD Error: one or more errors ocurred while gathering pod-specific data for namespace: openshift-etcd ....... [must-gather-np8xr] POD INFO: Audit logs for kube-apiserver collected. [must-gather-np8xr] POD WARNING: Collecting one or more service logs on ALL master nodes in your cluster. This could take a large amount of time. [must-gather-np8xr] POD INFO: Collecting host service logs for kubelet [must-gather-np8xr] POD INFO: Collecting host service logs for crio [must-gather-np8xr] POD INFO: Waiting for worker host service log collection to complete ... [must-gather-np8xr] POD INFO: Worker host service log collection to complete. [must-gather-np8xr] OUT waiting for gather to complete [must-gather-np8xr] OUT downloading gather output [must-gather-np8xr] OUT receiving incremental file list [must-gather-np8xr] OUT created directory must-gather.local.7355098706727993903 [must-gather-np8xr] OUT ./ [must-gather-np8xr] OUT audit_logs/ [must-gather-np8xr] OUT audit_logs/kube-apiserver.audit_logs_listing [must-gather-np8xr] OUT audit_logs/openshift-apiserver.audit_logs_listing [must-gather-np8xr] OUT audit_logs/kube-apiserver/ [must-gather-np8xr] OUT audit_logs/kube-apiserver/qesimard-ntly-04-1023-hdf8r-master-0-audit-2019-09-04T21-12-44.929.log.gz [must-gather-np8xr] OUT audit_logs/kube-apiserver/qesimard-ntly-04-1023-hdf8r-master-0-audit-2019-09-04T21-49-41.626.log.gz [must-gather-np8xr] OUT audit_logs/kube-apiserver/qesimard-ntly-04-1023-hdf8r-master-0-audit-2019-09-04T22-33-49.861.log.gz
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922