exasupport no longer outputs error traceback for incorrect arguments

Detail name	Value
Changelog Number	19661
Type	Bug
Status	Resolved
Affected Versions	Exasol 8.0.0
Fix Versions	Exasol 8.28.0
Resolution Date	2024-05-29

Description

When incorrect arguments are passed, exasupport used to output an error traceback:

[root@n11 ~]# exasupport -x 4
Traceback (most recent call last):
  File "/opt/exasol/cos-8.45.0/bin/exasupport", line 8, in <module>
    sys.exit(main())
  File "/opt/exasol/cos-8.45.0/lib/python3.10/site-packages/libconfd/cli/exasupport.py", line 8, in main
    request_logs, request_bts = support.postProcessArgs(args)
  File "/opt/exasol/cos-8.45.0/lib/python3.10/site-packages/libconfd/common/support.py", line 183, in postProcessArgs
    raise RuntimeError(f"Invalid value for -x/--exasolution-log-type: '{args.exasolution_log_type}'!")
RuntimeError: Invalid value for -x/--exasolution-log-type: '4'!

Workaround

There is no workaround.

Fix

Now it displays a user-friendlier error:

[root@n11 ~]# exasupport -x 4
Failed to process command-line arguments: Invalid value for -x/--exasolution-log-type: '4'!

Functionality is not affected.