action #125372
closed
o3 jobs failed with auto_review:"api failure: 403 response: timestamp mismatch":retry because chrony is not installed on w19+w20 size:M
Added by okurz about 1 year ago.
Updated about 1 year ago.
Category:
Regressions/Crashes
Description
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
- Assignee deleted (
okurz)
- Priority changed from Urgent to Normal
I called
for i in aarch64 openqaworker4 openqaworker7 openqaworker19 openqaworker20 qa-power8-3 rebel; do echo $i && ssh root@$i "zypper -n in chrony && systemctl enable --now chronyd" ; done
and locally within an os-autoinst/scripts checkout
bash -ex ./openqa-monitor-investigation-candidates | ./openqa-label-known-issues-multi
this should address the urgency
- Project changed from openQA Infrastructure to openQA Project
- Category set to Regressions/Crashes
- Subject changed from o3 jobs failed with auto_review:"api failure: 403 response: timestamp mismatch":retry because chrony is not installed on w19+w20 to o3 jobs failed with auto_review:"api failure: 403 response: timestamp mismatch":retry because chrony is not installed on w19+w20 size:M
- Description updated (diff)
- Status changed from New to Workable
- Status changed from Workable to In Progress
- Assignee set to livdywan
Looked at briefly in the Unblock. Looking into updating the dependencies based on the suggestions, ideally without hard-coding a specific service, should be clear enough and mainly not done yet because of more urgent tasks. So I'll take a look.
- Due date set to 2023-04-06
Setting due date based on mean cycle time of SUSE QE Tools
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
AC2 should now be fulfilled, no unexpected side-effects. Install docs also mention time sync now.
Also available in: Atom
PDF