RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1793060 - dsctl healthcheck issues error : type object 'datetime.date' has no attribute 'fromisoformat'
Summary: dsctl healthcheck issues error : type object 'datetime.date' has no attribute...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: 389-ds-base
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: mreynolds
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-20 15:26 UTC by sgouvern
Modified: 2023-04-20 15:16 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-1.4.2.4-7.module+el8.2.0+5670+0b8b1c2e
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:01:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 3889 0 None closed dsctl healthcheck issues error : type object 'datetime.date' has no attribute 'fromisoformat' 2021-01-11 17:03:25 UTC
Github 389ds 389-ds-base issues 3904 0 None closed Fix dsctl healthcheck for python36 2021-01-11 17:03:19 UTC
Red Hat Issue Tracker RHELPLAN-33104 0 None None None 2023-04-20 15:16:17 UTC
Red Hat Product Errata RHBA-2020:1703 0 None None None 2020-04-28 16:01:49 UTC

Comment 1 mreynolds 2020-01-20 16:19:28 UTC
This is happening because the code was written upstream which was using python 3.7, but RHEL is using python 3.6 which does not have "fromisoformat".  Need to work on a new approach...

Comment 2 mreynolds 2020-01-21 15:02:33 UTC
Upstream ticket:

https://pagure.io/389-ds-base/issue/50835

Comment 4 sgouvern 2020-02-27 10:51:01 UTC
Verified with 389-ds-base-1.4.2.8-2.module+el8dsrv+5809+6657a82a.x86_64

# dscreate interactive
# dsctl localhost healthcheck
Beginning lint report, this could take a while ...
Checking Backends ...
Checking Config ...
Checking Encryption ...
Checking FSChecks ...
Checking ReferentialIntegrityPlugin ...
Checking MonitorDiskSpace ...
Checking Replica ...
Checking Changelog5 ...
Checking DSEldif ...
Checking NssSsl ...
Healthcheck complete.
No issues found.

The error is fixed. Marking as verified

Comment 5 sgouvern 2020-02-27 13:32:05 UTC
Verified too on 389-ds-base-1.4.2.4-7.module+el8.2.0+5670+0b8b1c2e.x86_64

Comment 7 errata-xmlrpc 2020-04-28 16:01:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1703


Note You need to log in before you can comment on or make changes to this bug.