Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2255573

Summary: Timezone America/St_Johns is not properly represented in log timestamps
Product: Red Hat Directory Server Reporter: Chance Callahan <ccallaha>
Component: 389-ds-baseAssignee: LDAP Maintainers <idm-ds-dev-bugs>
Status: CLOSED MIGRATED QA Contact: LDAP QA Team <idm-ds-qe-bugs>
Severity: medium Docs Contact: Evgenia Martynyuk <emartyny>
Priority: unspecified    
Version: 11.0CC: dchen, idm-ds-dev-bugs, musoni, progier, tbordaz, vvanhaft
Target Milestone: DS12.5Keywords: Triaged
Target Release: dirsrv-12.5   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-26 13:53:16 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:

Description Chance Callahan 2023-12-22 00:08:26 UTC
Description of problem:
America/St_Johns has a UTC offset of -03:30.

# timedatectl
               Local time: Thu 2023-12-21 20:33:31 NST
           Universal time: Fri 2023-12-22 00:03:31 UTC
                 RTC time: Fri 2023-12-22 00:03:32
                Time zone: America/St_Johns (NST, -0330)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

RHDS shows a timezone offset in the logs of -031800 instead:

ns-slapd[67963]: [21/Dec/2023:20:29:56.032925110 -031800] - INFO - slapd_daemon - slapd started.  Listening on All Interfaces port 389 for LDAP requests

Version-Release number of selected component (if applicable):
* 389-ds-base-1.4.3.31-11.module+el8dsrv+17815+4f95348d.x86_64

How reproducible:
Confirmed by Red Hat Support.

Steps to Reproduce:
1. Install RHEL and set timezone to America/St_Johns
2. Setup a default instance of RHDS and start it.
3. Run timedatectl and compare the UTC offset to the one in the RHDS logs (systemctl status dirsrv@example).

Actual results:
RHDS shows a UTC offset of -03:18.

Expected results:
RHDS shows a UTC offset of -03:30.

Additional info:
N/A

Comment 1 Pierre Rogier 2024-01-02 11:53:19 UTC
Note: This bug impact all timezone whose shift in not a multiple of an hour.
The reason is that 389-ds-base/ldap/servers/slapd/time.c:format_localTime_hr_log() logs the timezone shift as SIGN HOUR SECONDS instead using ISO 8601 specification (i.e: SIGN HOUR MINUTES)
Fix is trivial (just have to divide the seconds by 60)

Comment 3 Ding-Yi Chen 2024-03-06 00:47:12 UTC
I have created a pull request to upstream main branch:

https://github.com/389ds/389-ds-base/pull/6118

Comment 5 Viktor Ashirov 2024-06-26 13:53:16 UTC
This BZ has been automatically migrated to Red Hat Issue Tracker https://issues.redhat.com/browse/DIRSRV-61. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.