389-ds-base

#51091 Healthcheck with --json option reports "Object of type 'bytes' is not JSON serializable" when mapping tree is deleted
Closed: wontfix by mreynolds. Opened by mreynolds.

Closed: wontfix
Reopen Issue

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1835619

Description of problem:
When mapping tree is deleted, healthcheck without --json argument reports
DSBLE0001 and DSBLE0003 codes correctly, but using healthcheck with --json
option ends in Error: Object of type 'bytes' is not JSON serializable.
Version-Release number of selected component (if applicable):
389-ds-base-1.4.2.4-8.module+el8.2.0+5959+cfcaedbd.x86_64
389-ds-base-1.4.2.12-1.fc31.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Create DS instance
2. Delete mapping tree:
# ldapdelete -p 389 -D "cn=directory manager" -w password -h server.example.com
'cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config'
3. Run healthcheck with --json option:
# dsctl --json inst healthcheck
Actual results:
# dsctl --json inst healthcheck
Error: Object of type 'bytes' is not JSON serializable
Expected results:
Healthcheck should return DSBLE0001 and DSBLE0003 issues in json format.
Additional info:

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

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

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

Metadata Update from @mreynolds:
- Issue priority set to: major
- Issue set to the milestone: 1.4.1 (was: 0.0 NEEDS_TRIAGE)

Commit 495ee204 relates to this ticket

Commit 495ee20 relates to this ticket

3bb6b5032..d3ae07a8d 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

a7430ed5a..703d85749 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

0fb23f3c5..41e0f4bc2 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Commit 4610b5f6 relates to this ticket

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

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 (was: fixed)
Metadata
None
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.