action #37009
closed
openqa-scripts repo sync on OSD disabled and tainted
Added by michalnowak almost 6 years ago.
Updated almost 6 years ago.
Description
Update of openqa-scripts in cron is disabled:
mnowak@openqa:~> tail -n1 /etc/cron.d/SLES.CRON
#*/5 * * * * root cd /opt/openqa-scripts && git fetch --all && git checkout --force "origin/master"
@coolo says the repo has some changes backed-out.
Make the repo sync again automatically. I need SLES 12 SP4 JeOS images synced to OSD.
I said "443ea63 is checked out, not master". And I can't say if this was reverted on purpose or just left stale. The disabled cron job has no comment.
So I'd suggest just to reenable the cron. But a little suggestion: git checkout --force is what created this situation. It would be better to stay on master and use git reset --hard origin/master
coolo wrote:
But a little suggestion: git checkout --force is what created this situation.
Then it definitely wasn't me as I never used that ;) I always use git reset --hard …
- Status changed from New to Resolved
- Assignee set to szarate
- Target version set to Current Sprint
- Difficulty set to easy
- Status changed from Resolved to In Progress
still tainted:
# git status
HEAD detached at origin/master
You are currently bisecting, started from branch '443ea63'.
(use "git bisect reset" to get back to the original branch)
- Status changed from In Progress to Resolved
- Target version changed from Current Sprint to Done
Also available in: Atom
PDF