Project

General

Profile

Actions

action #12128

closed

pushing needles from osd to gitlab fails but needle is present in repo

Added by okurz about 8 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2016-05-25
Due date:
% Done:

0%

Estimated time:

Description

observation

Sometimes commiting needles with the push to the needle gitlab repo can fail, e.g. see
see attached screenshot needle git commit fail

] Running cmd: git --git-dir /var/lib/openqa/share/tests/sle-12/products/sle/needles/.git --work-tree /var/lib/openqa/share/tests/sle-12/products/sle/needles push
[Wed May 25 16:14:05 2016] [17115:warn] GitLab: API is not accessible
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
[Wed May 25 16:14:05 2016] [17115:error] cmd returned non-zero value
[Wed May 25 16:14:05 2016] [17115:error] failed to git commit gnome_terminal-gnome-terminal-second-tab-20160525 at /usr/share/openqa/script/../lib/OpenQA/WebAPI/Controller/Step.pm line 392.

steps to reproduce

probably hard to reproduce unless you mock a non-available gitlab server

problem

Does not seem to happen often. Maybe a race condition or some issue with the gitlab server. I (okurz) don't know if this also has been seen on o3 pushing to github.

suggestion

  • At least the user feedback could be improved.
  • Retry with timeout and better user feedback

workaround

login manually to osd (or ask someone to do it) and try the push as user "geekotest", e.g. sudo -u geekotest git push from the needles repo working dir. Don't recreate the needle. git commits will be created.


Files


Related issues 1 (0 open1 closed)

Related to openQA Infrastructure - action #42920: Gitlab user gets blocked: Try out gitlab deployment tokens for openQAResolvednicksinger2018-10-25

Actions
Actions

Also available in: Atom PDF