Operational Defect Database
BugZero found this defect 33 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1291513
Some log messages/timestamps do not observe configured timezone
Last update date:
5/15/2024
Affected products:
F5OS
F5OS Velos
Affected releases:
F5OS-A 1.3.2
Fixed releases:
No fixed releases provided.
Description:
Bug ID 1291513: Some log messages/timestamps do not observe configured timezone ... Last Modified: May 15, 2024 ... 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
