Time zones are inconsistent across GitLab component logs when set to non-UTC time zone

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

Timezones are inconsistent across various system logs, ignoring GitLab global timezone setting

Steps to reproduce

  1. Set time zone of the operating system GitLab Omnibus instance is hosted to Asia/Tokyo (JST, +0900)
  2. Set time zone of the instance itself by following this document
  3. After you reconfigure and restart GitLab, timestamps recorded to certain component logs are JST, but most are still UTC.

/var/log/gitlab

  • gitlab-rails
    • production_json.log UTC
    • api_json.log UTC
  • sidekiq
    • current UTC
  • gitlay
    • current UTC, JST
  • postgresql
    • current UTC
  • redis
    • current. UTC, JST
  • gitlab-pages
    • current. JST

Example Project

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 
  (For installations with omnibus-gitlab package run and paste the output of: \\\`sudo gitlab-rake gitlab:env:info\\\`)  (For installations from source run and paste the output of: \\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\`)

System information System: Proxy: no Current User: git Using RVM: no Ruby Version: 3.2.8 Gem Version: 3.6.9 Bundler Version:2.7.1 Rake Version: 13.0.6 Redis Version: 7.2.10 Sidekiq Version:7.3.9 Go Version: unknown

GitLab information Version: 18.3.1-ee Revision: cb158597 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 16.8 URL: https://gitlab.nlw.local HTTP Clone URL: https://gitlab.nlw.local/some-group/some-project.git SSH Clone URL: git@gitlab.nlw.local:some-group/some-project.git Elasticsearch: yes Geo: no Using LDAP: yes Using Omniauth: yes Omniauth Providers:

GitLab Shell Version: 14.44.0 Repository storages:

Gitaly

Results of GitLab application Check

Expand for output related to the GitLab application check 
 (For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:check SANITIZE=true\`)  (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\`)  (we will only investigate if the tests are passing)

Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 14.44.0 ? ... OK (14.44.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/gitlab-shell-check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... no Try fixing it: sudo -u git -H RAILS_ENV=production bin/background_jobs start For more information see: doc/install/installation.md in section "Install Init Script" see log/sidekiq.log for possible errors Please fix the error above and rerun the checks.

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... Server: ldapmain LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results) User output sanitized. Found 21 users of 100 limit.

Checking LDAP ... Finished

Checking GitLab App ...

Database config exists? ... yes Tables are truncated? ... skipped All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Cable config exists? ... yes Resque config exists? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Systemd unit files or init script exist? ... skipped (omnibus-gitlab has neither init script nor systemd units) Systemd unit files or init script up-to-date? ... skipped (omnibus-gitlab has neither init script nor systemd units) Projects have namespace: ... 1/1 ... yes 35/2 ... yes 34/3 ... yes 34/4 ... yes 53/7 ... yes 53/8 ... yes 53/9 ... yes 73/13 ... yes 73/14 ... yes 67/32 ... yes 95/33 ... yes 102/34 ... yes 99/36 ... yes 99/37 ... yes 104/38 ... yes 107/39 ... yes 102/40 ... yes 109/41 ... yes 109/42 ... yes 124/43 ... yes 98/44 ... yes 109/45 ... yes 121/46 ... yes 117/47 ... yes 117/48 ... yes 117/49 ... yes 121/50 ... yes 102/51 ... yes 124/52 ... yes 135/53 ... yes 157/54 ... yes 135/55 ... yes 138/56 ... yes 138/57 ... yes 135/58 ... yes 142/59 ... yes 142/60 ... yes 142/61 ... yes 91/63 ... yes 159/65 ... yes 164/66 ... yes 135/68 ... yes 172/69 ... yes 150/70 ... yes 150/71 ... yes 178/74 ... yes 178/75 ... yes 172/77 ... yes 159/82 ... yes 90/84 ... yes 201/86 ... yes 208/88 ... yes 208/89 ... yes 208/90 ... yes 35/91 ... yes 159/92 ... yes 159/93 ... yes 159/94 ... yes 35/95 ... yes 159/96 ... yes 90/97 ... yes 90/98 ... yes 35/99 ... yes 159/100 ... yes 159/101 ... yes 159/102 ... yes 1/103 ... yes 66/104 ... yes 201/105 ... yes 201/106 ... yes 201/107 ... yes 201/108 ... yes 201/109 ... yes 34/110 ... yes 34/111 ... yes 34/112 ... yes 34/113 ... yes 90/114 ... yes 34/115 ... yes 34/116 ... yes 90/117 ... yes 34/118 ... yes 34/119 ... yes 34/120 ... yes 34/121 ... yes 34/122 ... yes 263/124 ... yes 267/125 ... yes 34/126 ... yes 258/127 ... yes 34/128 ... yes 34/129 ... yes 280/130 ... yes 282/131 ... yes 34/132 ... yes 35/133 ... yes 34/134 ... yes Redis version >= 6.2.14? ... yes Ruby version >= 3.0.6 ? ... yes (3.2.8) Git user has default SSH configuration? ... yes Active users: ... 34 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes Elasticsearch version 7.x-9.x or OpenSearch version 1.x-3.x ... yes (elasticsearch 9.1.3) All migrations must be finished before doing a major upgrade ... yes

Checking GitLab App ... Finished

Checking GitLab subtasks ... Finished

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by Yohei Kawase