The CLI tools should be catching all exceptions, displaying a friendly error message, and returning a rc code of 1.
$ dsconf -j ldap://localhost:389 backend list Traceback (most recent call last): File "./dsconf", line 121, in <module> inst = connect_instance(dsrc_inst=dsrc_inst, verbose=args.verbose) File "/home/mareynol/source/ds389/389-ds-base/src/lib389/lib389/cli_base/__init__.py", line 92, in connect_instance raise Exception("Must provide a binddn to connect with") Exception: Must provide a binddn to connect with
This should just be:
$ dsconf ldap://localhost:389 backend list Error: Must provide a binddn to connect with $ echo $? 1
Metadata Update from @mreynolds: - Issue assigned to mreynolds
The following Ticket/PR is addressing this issue:
https://pagure.io/389-ds-base/issue/49712
https://pagure.io/389-ds-base/pull-request/49776
Closing this ticket as a duplicate.
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2775
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: duplicate)
Login to comment on this ticket.