Description
Problem
If one gives an invalid output directory to collect logs the returned error is very vage and looks as follows:
% cbbackupmgr collect-logs -a s3://cloud-bucket/archive --obj-staging-dir ~/backup/staging --obj-endpoint http://localhost:4566 --obj-region region --obj-access-key-id key_id --obj-secret-access-key key --s3-force-path-style -o ~/backup/collects
|
Collecting logs from s3://cloud-bucket/archive failed: no such file or directory
|
The error message makes it look like the archive does not exist when instead is the output directory which is wrong.
Expectation
A more infomrative error of the form "output directory /x/y/z does not exist"
Attachments
Issue Links
- is duplicated by
-
MB-50364 Incorrect error with cbbackupmgr collect-log and --output-dir
- Closed