Bug ID 1291513: Some log messages/timestamps do not observe configured timezone

Last Modified: Oct 21, 2024

Affected Product(s):
F5OS Velos(all modules)

Known Affected Versions:
F5OS-A 1.3.2

Fixed In:
F5OS-A 1.8.0

Opened: Apr 21, 2023

Severity: 3-Major

Symptoms

Some logfiles and timestamps report the time as UTC even when the system is configured with a non-UTC timezone.

Impact

Difficult to correlate timestamps across log files.

Conditions

The orchestration-manager is not aware of the configured timezone, so Openshift/Kubernetes/Ansible log files produced by this component are reported as UTC. Also, the 'user login/last login' times reported by the CLI are always in UTC.

Workaround

None

Fix Information

Orchestration Manager recognizes the current timezone setting, and produces all timestamps as localtime using RFC3339 format (localtime + offset). All debug logfiles produced by this component are now timezone aware. The sshd/login programs report login/last login times as localtime, not UTC. The CLI no longer (incorrectly) reports login time.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips