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 1990002 - monitor displays wrong date for connection
Summary: monitor displays wrong date for connection
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: 389-ds-base
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.6
Assignee: mreynolds
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On:
Blocks: 2066848
TreeView+ depends on / blocked
 
Reported: 2021-08-04 14:29 UTC by mreynolds
Modified: 2022-05-10 14:11 UTC (History)
5 users (show)

Fixed In Version: 389-ds-1.4-8060020211021200750.ce3e8c9c
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2066848 (view as bug list)
Environment:
Last Closed: 2022-05-10 13:43:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker IDMDS-1732 0 None None None 2021-10-20 15:30:02 UTC
Red Hat Issue Tracker IDMDS-1737 0 None None None 2021-10-21 21:00:58 UTC
Red Hat Issue Tracker RHELPLAN-92343 0 None None None 2021-08-04 14:30:42 UTC
Red Hat Product Errata RHBA-2022:1815 0 None None None 2022-05-10 13:43:29 UTC

Description mreynolds 2021-08-04 14:29:26 UTC 
Description of problem:


Looks like a epoch date is used for new connections. Maybe it's related to the REALTIME vs MONOTONIC clock change we did recently?

# dsconf localhost monitor server
dn: cn=monitor
version: 389-Directory/2.0.3.20210306gitf0938dada B2021.065.1543
connection: 472:19700102065831Z:1:1:-:cn=dm:0:0:0:38323:ip=::1
connection: 473:19700102065834Z:3:2:-:cn=dm:0:0:0:38324:ip=local


Needs to do into 8.3.z, 8.4.z, 8.5.z


Upstream ticket:

https://github.com/389ds/389-ds-base/issues/4658
Comment 3 sgouvern 2021-11-04 14:01:09 UTC 
With 389-ds-base-1.4.3.28-1.module+el8.6.0+13040+7da9aab8.x86_64 

The patch from https://github.com/389ds/389-ds-base/issues/4658 seems to be correctly applied to the build, but it seems it does not fix the issue :

# dsconf inst1 monitor server
dn: cn=monitor
version: 389-Directory/1.4.3.28 B2021.294.2026
threads: 16
connection: 1:20211104135228Z:3:2:-:cn=Directory Manager:0:0:0:1:ip=local
Comment 4 mreynolds 2021-11-04 16:31:00 UTC 
(In reply to sgouvern from comment #3)
> With 389-ds-base-1.4.3.28-1.module+el8.6.0+13040+7da9aab8.x86_64 
> 
> The patch from https://github.com/389ds/389-ds-base/issues/4658 seems to be
> correctly applied to the build, but it seems it does not fix the issue :
> 
> # dsconf inst1 monitor server
> dn: cn=monitor
> version: 389-Directory/1.4.3.28 B2021.294.2026
> threads: 16
> connection: 1:20211104135228Z:3:2:-:cn=Directory Manager:0:0:0:1:ip=local

This date looks correct to me.  Previously the incorrect date was 19700102065834Z 

Am I missing something?
Comment 6 sgouvern 2021-11-05 08:51:56 UTC 
My bad, I had in mind we expected also the date to be in a more human readable format.
marking as verified
Comment 12 errata-xmlrpc 2022-05-10 13:43:00 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 (389-ds:1.4 bug fix and enhancement update), 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-2022:1815
Note You need to log in before you can comment on or make changes to this bug.