Bug 1868343

Description of problem:

Customer following https://access.redhat.com/solutions/4929021 gets error. As i'm working on sev1 case, I need well tested and working tool to benchmark ETCD as customer are sometimes overloading servers without properly scaling up the performance of storage.

Another suggestion could be to use dd as mentioned in 02657219 (and notes below). As dd is part of RHCOS/RHEL, maybe we should ditch Toolbox (as it's other team(?) responsibility) and go with most simple and stable solution.

ps: Frankly I don't care which tool will be chosen, but let's make sure it's well tested with every release and it's well documented. 

Justification for HIGH severity of BZ:
Suggesting tool that may or may not work, doesn't help with sev1 cases when troubleshooting speed is crucial, and also doesn't make us look good in customer's eyes as we're suggesting the solution that doesn't work. Please make choosing proper tool and documenting it's use priority. thanks a lot.


[ERROR]

[admin.openline@rosbas ~]$ oc debug node/rosmas501.liander04.openshift.openline.nl
Starting pod/rosmas501liander04openshiftopenlinenl-debug ...
To use host binaries, run `chroot /host`
Pod IP: 10.248.126.10
If you don't see a command prompt, try pressing enter.
sh-4.2# chroot /host /bin/bash
[root@xxx /]# vi /root/.toolboxrc
[root@xxx /]# toolbox
.toolboxrc file detected, overriding defaults...
Trying to pull docker.io/fedora:latest...
Getting image source signatures
Copying blob c7def56d621e done
Copying config a368cbcfa6 done
Writing manifest to image destination
Storing signatures
a368cbcfa6789bc347345f6d19132afe138b62ff5373d2aa5f37120277c90b54
Error: docker.io/fedora:latest does not have a label of RUN
Spawning a container 'toolbox-' with image 'docker.io/fedora:latest'
eaa0fdba3d54d06e0063a7e9aeede39ecdc53d3dbfd8464ac57b4bb93d523a73
toolbox-
Container started successfully. To exit, type 'exit'.
Error: exec failed: container_linux.go:349: starting container process caused "open /proc/self/task/22/attr/exec: no such file or directory": OCI runtime command not found error


Version-Release number of selected component (if applicable):

OCP 4.3.8


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

No matter what tool we suggest, I expect it to be well tested and working.. and ideally put in our documentation (in new troubleshooting part as in 4.5).


Additional info:

See 02657219 and comments #220 #230 for using dd as another option