389-ds-base

#51136 dsctl does not report errors in json
Closed: wontfix by mreynolds. Opened by mreynolds.

Closed: wontfix
Reopen Issue

Issue Description

If dsctl is called with the json object --json the error needs to be in JSON too. This is breaking the UI when something goes wrong with dsctl like an instance failing to start

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1751224

https://pagure.io/389-ds-base/pull-request/51139

Commit af870480 fixes this issue

Commit af87048 fixes this issue

3d98eb10a..a8eca1add 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

dbae8c8fd..d3e9456ca 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

Metadata Update from @mreynolds:
- Issue close_status updated to: None (was: Fixed)

https://pagure.io/389-ds-base/pull-request/51210

22c514914..632a8e085 master -> origin/master
48572f6c6..d6ca851eb 389-ds-base-1.4.2 -> 389-ds-base-1.4.2
7624c59bc..7c089195f 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

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/4189

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
Metadata
None

CLI Cockpit

None
None
Normal
None
None
Related Pull Requests
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.