action #125372
Updated by mkittler about 1 year ago
## Observation From https://suse.slack.com/archives/C02CANHLANP/p1677855113118989 https://openqa.opensuse.org/tests/3154313 on w19 failed with "api failure: 403 response: timestamp mismatch". I checked and found that chrony isn't installed on w19+20 and the clock is off by 5m. ## Acceptance criteria * **AC1:** Jobs on w19+w20 don't fail due to timestamp mismatch * **AC2:** New host installations are ensured to include a time sync daemon ## Suggestions * Install and enable chrony now * Add a dependency in packages (e.g. to the generic provide `ntp-daemon`) * Consider mentioning the requirement in docs * Make the error message more unfriendly (to state the an out-of-sync clock might be the source of the problem) * Look at time-sync.target (maybe that is a generic target we can depend on) * Maybe split out the dependency on systemd-level into another ticket