fluid icon indicating copy to clipboard operation
fluid copied to clipboard

[BUG] diagnose script is not working working properly

Open lizzzcai opened this issue 3 years ago • 0 comments

What is your environment(Kubernetes version, Fluid version, etc.) Fluid: main Kubernetes: 1.21.10 Describe the bug

the diagnose-fluid.sh is not working properly following this doc.

  1. errors in some of the log files. (unknown timeout command)
  2. logs in fuse sidecar under serverless mode are not captured.

error example:

-----------------run helm get all -n demo fluid------------------
./diagnose-fluid.sh: line 22: timeout: command not found
failed to collect info: helm get all -n demo fluid
------------End of helm----------------


-----------------run helm get all -n demo s3-data------------------
./diagnose-fluid.sh: line 22: timeout: command not found
failed to collect info: helm get all -n demo s3-data
------------End of helm----------------


-----------------run kubectl get po -owide -n demo------------------
./diagnose-fluid.sh: line 22: timeout: command not found
failed to collect info: kubectl get po -owide -n demo
------------End of kubectl----------------


Error from server (NotFound): persistentvolumes "s3-data" not found


What you expect to happen:

diagnose script can be run without error and capture all the information.

How to reproduce it

diagnose a application under fluid serverless mode.

Additional Information

lizzzcai avatar May 19 '22 04:05 lizzzcai