Description of problem (please be detailed as possible and provide log snippests): must gather is using `noobaa diagnose --dir` for diagnostic and output the stdout to a file. `noobaa diagnose --dir` just states that it is collecting the diag but the diag themselves are collected in a tar file located in the dir specified in --dir flag. We need to collect the tar file. Version of all relevant components (if applicable): 4.6 Can this issue reproducible? Yes Actual results: NooBaa diag tar is not collected Expected results: NooBaa diag tar should be collected
Created attachment 1726904 [details] terminal of must-gather collection Verified on a vsphere internal mode cluster with OCS version = ocs-operator.v4.6.0-154.ci and OCP = 4.6.0-0.nightly-2020-11-05-024238 Noobaa-diagnostics zipped file is collected within noobaa/raw_output folder >> snip from terminal [must-gather-5klch] POD collecting oc command clusterrolebinding [must-gather-5klch] POD receiving incremental file list [must-gather-5klch] POD noobaa-operator [must-gather-5klch] POD [must-gather-5klch] POD sent 43 bytes received 58,991,064 bytes 39,327,404.67 bytes/sec [must-gather-5klch] POD total size is 58,976,582 speedup is 1.00 [must-gather-5klch] POD collecting dump of obc list [must-gather-5klch] POD collecting dump of status ... ... [must-gather-5klch] OUT noobaa/raw_output/ [must-gather-5klch] OUT noobaa/raw_output/noobaa_diagnostics_2020-11-05T14:51:39Z.tar.gz [must-gather-5klch] OUT noobaa/raw_output/status ---------------------------------- $ ls -ltrh must-gather.local.3474338440678756329/quay-io-rhceph-dev-ocs-must-gather-sha256-87129c2124ed57e69eff5e20f8e4438ee602a30e6868ecbe581acd7d3ef4070a/noobaa/raw_output/ total 124K -rw-r--r--. 1 nberry nberry 1.7K Nov 5 20:21 status -rw-r--r--. 1 nberry nberry 119K Nov 5 20:21 noobaa_diagnostics_2020-11-05T14:51:39Z.tar.gz @pulkit is there anything else needed to be verified before moving this BZ to verified state?
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 (Moderate: Red Hat OpenShift Container Storage 4.6.0 security, bug fix, enhancement update), 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/RHSA-2020:5605