action #38747
closed[tools] Needles from the OSD web editor do not get pushed to gitlab any longer
0%
Description
https://gitlab.suse.de/openqa/os-autoinst-needles-sles/commits/master shows the last commit 2 days ago. I was unable to find any hints on OSD why it stopped committing/pushing.
Last logs I found:
openqa:~ # xzcat /var/log/openqa.*xz | grep -i gitlab
[2018-07-20T04:19:30.0837 CEST] [debug] [pid:17746] To gitlab.suse.de:openqa/os-autoinst-needles-sles.git
[2018-07-20T04:19:48.0493 CEST] [debug] [pid:2371] To gitlab.suse.de:openqa/os-autoinst-needles-sles.git
[2018-07-20T02:51:06.0593 CEST] [debug] [pid:30899] To gitlab.suse.de:openqa/os-autoinst-needles-sles.git
Updated by okurz over 6 years ago
/var/lib/openqa/share/tests/sle/products/sle/needles/ is currently not on any branch.
Updated by okurz over 6 years ago
- Project changed from openQA Project (public) to openQA Tests (public)
- Subject changed from Needles from the OSD web editor do not get pushed to gitlab any longer to [tools] Needles from the OSD web editor do not get pushed to gitlab any longer
- Category changed from 128 to Infrastructure
- Priority changed from Normal to Urgent
It's an issue in our own infrastructure, [tools], please support here.
Updated by okurz over 6 years ago
- Status changed from New to In Progress
- Assignee set to okurz
Updated by okurz over 6 years ago
- Status changed from In Progress to Workable
- Assignee deleted (
okurz) - Priority changed from Urgent to Normal
/var/spool/mail/geekotest shows the email error reports from the cron jobs, e.g.
From geekotest@linux.site Fri Jul 20 07:30:22 2018
Return-Path: <geekotest@linux.site>
X-Original-To: geekotest
Delivered-To: geekotest@linux.site
Received: by linux.site (Postfix, from userid 1001)
id 1921B9D7E; Fri, 20 Jul 2018 07:30:22 +0200 (CEST)
From: "(Cron Daemon)" <geekotest@linux.site>
To: geekotest@linux.site
Subject: Cron <geekotest@openqa> env updateall=1 /usr/share/openqa/script/fetchneedles
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
Precedence: bulk
X-Cron-Env: <XDG_SESSION_ID=118204>
X-Cron-Env: <XDG_RUNTIME_DIR=/run/user/1001>
X-Cron-Env: <LC_CTYPE=en_US.UTF-8>
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/var/lib/openqa>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=geekotest>
X-Cron-Env: <USER=geekotest>
Message-Id: <20180720053022.1921B9D7E@linux.site>
Date: Fri, 20 Jul 2018 07:30:13 +0200 (CEST)
Status: O
fatal: update_ref failed for ref 'refs/heads/master': cannot lock ref 'refs/heads/master': is at 32973dbfc5f034ff21e2723f5e99fc79862313ca but expected eb91c9d18cdec6edd2c594784a59a6fa6b4c926f
Could not move back to refs/heads/master
error: cannot lock ref 'refs/remotes/origin/master': is at 32973dbfc5f034ff21e2723f5e99fc79862313ca but expected eb91c9d18cdec6edd2c594784a59a6fa6b4c926f
You are not currently on a branch.
Please specify which branch you want to rebase against.
See git-rebase(1) for details.
git rebase <branch>
It seems for a very long time the needles repo was not updated properly.
What I did as user "geekotest":
cd /var/lib/openqa/share/tests/sle/products/sle/needles
git remote update
git branch temp
git pull --rebase origin master
<skip conflicting patches as the needles are already created over gitlab MR>
git push origin HEAD:master
git checkout master
git pull --rebase origin master
git branch -D temp
so the needle repo is ok again but the original problem – whatever it was in detail – can still reappear.
And I think we have a Schroedinger-Bug in https://gitlab.suse.de/openqa/salt-states-openqa/blob/master/etc/master/cron.d/SLES.CRON#L20 . Trying to push the test repo to github should not work. This should be the internal needles repo!
-> https://gitlab.suse.de/openqa/salt-states-openqa/merge_requests/52 to fix that.
Updated by okurz almost 6 years ago
- Related to action #42920: Gitlab user gets blocked: Try out gitlab deployment tokens for openQA added
Updated by okurz almost 5 years ago
- Status changed from Workable to Resolved
- Assignee set to okurz
should be solved with openQA commit 2aadd3e56