Bug 1815088

Description of problem (please be detailed as possible and provide log
snippests):
It is noticed that running noobaa cluster diagnotics doesn't capture some of the command outputs as the binaries doesn't exist in the noobaa-core-0 pod.

===================================================
$ cat diagnostics_collection.log 
collected /var/log/messages files successfully

collected chkconfig.out successfully

collecting /log/nbfedump directory failed with error: Error: cp -fpR /log/nbfedump /tmp/diag exited with error Error: Command failed: cp -fpR /log/nbfedump /tmp/diag
cp: cannot stat '/log/nbfedump': No such file or directory


collecting slabtop.out failed with error: Error: slabtop -o &> /tmp/diag/slabtop.out exited with error Error: Command failed: slabtop -o &> /tmp/diag/slabtop.out


collecting top.out failed with error: Error: COLUMNS=512 top -c -b -n 1 &> /tmp/diag/top.out exited with error Error: Command failed: COLUMNS=512 top -c -b -n 1 &> /tmp/diag/top.out


collecting client_noobaa.log failed with error: Error: cp -fp /log/client_noobaa.log* /tmp/diag exited with error Error: Command failed: cp -fp /log/client_noobaa.log* /tmp/diag
cp: cannot stat '/log/client_noobaa.log*': No such file or directory


collecting noobaa_deploy.log failed with error: Error: cp -fp /log/noobaa_deploy* /tmp/diag exited with error Error: Command failed: cp -fp /log/noobaa_deploy* /tmp/diag
cp: cannot stat '/log/noobaa_deploy*': No such file or directory


collected supervisor logs successfully

collected df.out successfully

collected noobaa.log files successfully

finished get_system_collections_dump successfully

finished writing hosts list successfully

collected statistics successfully

collected lsof.out successfully

========================================================

In above `top` command is missing which is helpful to understand noobaa-core-0 db container high cpu usage causes.

Version of all relevant components (if applicable):
OCS v4.2.2
OCP 4.3.1

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No. However it affects during troubleshooting.

Is there any workaround available to the best of your knowledge?
Not in my knowledge.

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
3

Can this issue reproducible?
Yes.

Can this issue reproduce from the UI?
Yes.

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Download the Diagnostics from Noobaa console.
System Management -> Support & Diagnostics -> Download Diagnostics.
2. Check the contents of */tmp/diag from the archive.
3.


Actual results:
diag]$ cat top.out 
/bin/sh: top: command not found

diag]$ cat slabtop.out 
/bin/sh: slabtop: command not found
$

Expected results:
diagnostics_collection should not fail for some outputs. 

Additional info:
It is also noticed that `ps` command is not present inside the noobaa pods.