Description of problem (please be detailed as possible and provide log snippests): ================================================================================= Why this RFE needed: Currently ocs must-gather is collecting OBCs only in the yaml format. It can be difficult and time consuming for someone who wants to know the details of all OBCs present on the cluster as we need to go through each and every yamls named with bucket name (eg oc-bucket-6239c9a1965549049f2c6162f216a309.yaml) What are the Benefits: If we start collecting the obc raw output we can have following benefits, - We can easily see what are all obcs are present and its various parameters like namespace, bucket-name, its phase etc - Using this collective information it will be easy to replicate and build similar configurations in tests. Version of all relevant components (if applicable): ocs-olm-operator:4.4.0-416.ci Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: =================== 1) Create an OCS setup. 2) Create noobaa OBCs in different namespaces. 3) Collect OCS must-gather. Actual results: =============== ocs mus-gather collects noobaa obcs in yaml format. Expected results: ================= ocs mus-gather should collect noobaa obc list in raw output. Also it should collect from all namespaces. Additional info:
Raz, can you ack this for 4.5?
acked
One more patch needed: https://github.com/openshift/ocs-operator/pull/588
https://github.com/openshift/ocs-operator/pull/606 backport PR
Tested on: 4.5.0-0.nightly-2020-08-06-014216 Created a new namespace with Nooba OBC using the UI. Collected the must-gather logs using: oc adm must-gather --image=quay.io/rhceph-dev/ocs-must-gather:latest-4.5 The collection includes the newly created project OBC yaml as expected. For example, the collection had the Nooba OBC yaml in this location: <must_gather_logs_dir>/must-gather.local.1347373263558629025/quay-io-rhceph-dev-ocs-must-gather-sha256-2768a5eb6162307681d8dc35fc431c5a59a71cac1b7de98e7bdef851431a9ba3/namespaces/yosi-proj-bz-1833880/objectbucket.io/objectbucketclaims/yosi-obc-bz-1833880.yaml Moving to VERIFIED
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 (Red Hat OpenShift Container Storage 4.5.0 bug fix and 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/RHBA-2020:3754