In an effort to troubleshoot CSN time skew we should log a message when a large jump is detected, and we should also be checking for the errors returned by the "time" functions.
https://pagure.io/389-ds-base/pull-request/51096
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=1837105
New PR:
https://pagure.io/389-ds-base/pull-request/51109
Commit 2fc834a relates to this ticket
0478929..f8502d0 389-ds-base-1.4.3 -> 389-ds-base-1.4.3
09832ae..b709451 389-ds-base-1.4.2 -> 389-ds-base-1.4.2
963cdf8..b5d3327 389-ds-base-1.4.1 -> 389-ds-base-1.4.1
33b72ca..6f14ce5 389-ds-base-1.3.10 -> 389-ds-base-1.3.10
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/4148
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.