Bug 1793060

Summary: dsctl healthcheck issues error : type object 'datetime.date' has no attribute 'fromisoformat'
Product: Red Hat Enterprise Linux 8 Reporter: sgouvern
Component: 389-ds-baseAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: RHDS QE <ds-qe-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.2CC: lkrispen, pasik, spichugi, tbordaz, vashirov
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:01:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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