Actions
action #153013
open[openQA][repo][error] openQA instance keeps reporting "dubious ownership" error when test run starts
Start date:
2024-01-02
Due date:
% Done:
0%
Estimated time:
Description
Observation¶
Following errors keep showing up in autoinst-log.txt from each test run on my personal openQA instance.
First the machine on which this openQA instance run has been given a fresh reinstall. It runs new Leap 15.5 system.
Second I installed openQA on this machine by using
curl -s https://raw.githubusercontent.com/os-autoinst/openQA/master/script/openqa-bootstrap | bash -x
So I do not think there is environmental issue with this machine and system.
Every time a test run starts, following "dubious ownership" errors reported in autoinst-log.txt:
[2024-01-02T20:43:50.930410+08:00] [debug] [pid:4064] git hash in 'sle-micro': 2732d91d808f8abfc07f1e9d7e571c0ebb3ab1d4
fatal: detected dubious ownership in repository at '/var/lib/openqa/share/tests/opensuse'
To add an exception for this directory, call:
git config --global --add safe.directory /var/lib/openqa/share/tests/opensuse
[2024-01-02T20:43:50.932239+08:00] [debug] [pid:4064] git url in 'sle-micro': UNKNOWN (origin remote not found)
[2024-01-02T20:43:51.167389+08:00] [debug] [pid:4064] git hash in 'sle-micro/products/sle-micro/needles': 60aef425dcfc1e2b6214d69869c8bf52ed48ca25
fatal: detected dubious ownership in repository at '/var/lib/openqa/share/tests/opensuse/products/sle-micro/needles'
To add an exception for this directory, call:
git config --global --add safe.directory /var/lib/openqa/share/tests/opensuse/products/sle-micro/needles
[2024-01-02T20:43:51.169498+08:00] [debug] [pid:4064] git url in 'sle-micro/products/sle-micro/needles': UNKNOWN (origin remote not found)
The error still persists even after executing
git config --global --add safe.directory xxx
I attached autoinst-log.text at this comment
Steps to reproduce¶
- Every time test run starts
Impact¶
- No sure whether openQA functions as normal because errors start showing up at the very beginning and before loading test modules
- These errors look not trivial because they are related to test engine.
- autoinst-log.text becomes less convincing because.
Problem¶
Looks like some wrong with test engine and repo itself.
Suggestions¶
- What needs to be fixed ?
- What setting needs to be adjusted ?
Workaround¶
n/a
Files
Actions