action #69718
closedcoordination #161414: [epic] Improved salt based infrastructure management
harmonize timezone used for our machines size:M
0%
Description
Motivation¶
Has been first reported in #62309#note-3 that our workers use inconsistent timezone which makes reading and especially comparing logs harder. Also see #65118#note-29 for another related reported. We should use UTC on all machines to have something fair for all our users and employees regardless where they are situated, without time jumps and consistent.
Acceptance criteria¶
- AC1: All machines used within OSD infrastructure use UTC consistently for their internal timezone
- AC2: autoinst-log.txt files show UTC for new logs
Suggestions¶
- Either just change the timezone on all machines once and hope that in reinstalls we ensure the same and/or salt with https://docs.saltstack.com/en/latest/ref/states/all/salt.states.timezone.html#management-of-timezones
Updated by mkittler 8 months ago
I would also like to change the default in Grafana. We would just have to change a single line in /etc/grafana/grafana.ini:
# Default timezone for user preferences. Options are 'browser' for the browser local timezone or a timezone name from IANA Time Zone database, e.g. 'UTC' or 'Europe/Amsterdam' etc.
default_timezone = UTC
Updated by okurz about 1 month ago
- Status changed from Resolved to Workable
- Priority changed from Low to Normal
- Parent task set to #161414
Apparently only openQA worker+webUI were changed, also see https://suse.slack.com/archives/C02CANHLANP/p1737465467585649
@qa-tools Can we change timezone settings in z/kvm workers please?
Some tests are detecting time backwards jump as the test VM is configured with UTC, but the host has CET and during boot it confuses chrony
Updated by dheidler about 1 month ago
- Status changed from Workable to Feedback
Updated by jbaier_cz 24 days ago
- Related to action #175989: Too big logfiles causing failed systemd services alert: logrotate (monitor, openqaw5-xen, s390zl12) size:S added