action #170464
closed
openQA Project (public) - coordination #58184: [saga][epic][use case] full version control awareness within openQA
openQA Project (public) - coordination #152847: [epic] version control awareness within openQA for test distributions
Enable automatic openQA git clone instead of fetchneedles on o3
Added by livdywan 15 days ago.
Updated 15 days ago.
Category:
Feature requests
Description
Motivation¶
We have a new feature called git_auto_update (see #164898). The implementation highlighted areas that needed to be improved before it can be used in production. Provided all blockers are addressed we should enable this on o3.
Acceptance criteria¶
- AC1: Git repos are updated via a minion jobs
- AC2: Cron jobs are no longer needed
Suggestions¶
- See #166721#note-15 for context
- Disable cron job as a first thing
- Just enable the automatic cloning either first manually or directly via salt
- Monitor the impact, e.g. failed minion jobs or stalled minion jobs or not enough jobs picked up or executed in time, see also job-related queries on Grafana
- Enable new systemd timer
- Parent task set to #152847
- Tags changed from infra, o3 to o3
- Target version set to Ready
- Status changed from New to Rejected
- Assignee set to okurz
Wait. This is a duplicate of #168379 . When automatic_git_clone is enabled by default then it will be used on o3
- Status changed from Rejected to Feedback
okurz wrote in #note-3:
Wait. This is a duplicate of #168379 . When automatic_git_clone is enabled by default then it will be used on o3
Well, that ticket is about osd. I'm not so sure about letting things happen implicitly - unless you want to make #168379 cover both retroactively?
- Related to action #168376: Enable automatic openQA git clone instead of fetchneedles on OSD size:S added
- Related to action #164898: Replace fetchneedles with a minion job for the regular update of git repos size:M added
tinita wrote in #note-7:
o3 was done as part of #164898
Well when I asked in Slack you said it's not enabled. Are you saying it is enabled? Or should that ticket be re-opened? Feel free to go ahead and update either ticket I guess.
livdywan wrote in #note-8:
Well when I asked in Slack you said it's not enabled. Are you saying it is enabled? Or should that ticket be re-opened? Feel free to go ahead and update either ticket I guess.
I said I think it is not enabled. I thought you would check first.
It is enabled explicitly on o3, but not on osd
# o3
% grep auto_update /etc/openqa/openqa.ini
git_auto_update = yes
% cat /etc/cron.d/openqa-update-git
...
# tina 2024-10-16 replace by git_auto_update https://progress.opensuse.org/issues/164898
#-*/1 * * * * geekotest env updateall=1 force=1 /usr/share/openqa/script/fetchneedles > /dev/null 2>&1
- Status changed from Feedback to Rejected
Fair enough. Sorry for the confusion.
Also available in: Atom
PDF