action #133520
Updated by tinita 10 months ago
I need to setup openqa from scratch and run into an issue which is not easy to find the reason. ``` -- zaoliang@quake1:~> sudo openqa-clone-custom-git-refspec -v https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17504 https://openqa.opensuse.org/tests/3461697 --apikey F5DEEB04FA524E0C --apisecret 5F150614E484ACCB [sudo] Passwort für root: /usr/bin/openqa-clone-custom-git-refspec: unrecognized option '--apikey' /usr/bin/openqa-clone-custom-git-refspec: unrecognized option '--apisecret' Usage: openqa-clone-custom-git-refspec <github_pr_url> <openqa_job_url> [CUSTOM_TEST_VAR_1=foo] [CUSTOM_TEST_VAR_2=bar] ... openqa-clone-custom-git-refspec <github_branch_url> <openqa_job_url> [CUSTOM_TEST_VAR_1=foo] [CUSTOM_TEST_VAR_2=bar] ... Options: -v, --verbose execute with verbose output -h, -?, --help display this help -n, --dry-run execute in dry-run mode, do not clone any openQA jobs -c --clone-job-args pass additional parameters to 'openqa-clone-job', e.g. '--clone-job-args="--show-progress"'. The default parameters are '--skip-chained-deps --parental-inheritance --within-instance' defined in the env variable $clone_args. Examples: openqa-clone-custom-git-refspec https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6529 https://openqa.opensuse.org/tests/835060 DESKTOP=textmode openqa-clone-custom-git-refspec https://github.com/coolgw/os-autoinst-distri-opensuse/tree/nfs https://openqa.opensuse.org/tests/835060 DESKTOP=textmode openqa-clone-custom-git-refspec -n -c '--show-progress' https://github.com/coolgw/os-autoinst-distri-opensuse/tree/nfs https://openqa.opensuse.org/tests/835060 DESKTOP=textmode openqa-clone-custom-git-refspec https://github.com/foursixnine/os-autoinst-distri-opensuse/tree/oopsitsbrokenagain https://openqa.opensuse.org/tests/3128467 NEEDLES_DIR='https://github.com/foursixnine/os-autoinst-needles-opensuse.git#oopsitsbrokenagain' You need to set the environment variable GITHUB_TOKEN to use authenticated requests. -- ``` The problem is access permission of /etc/openqa/client.conf. At least user should be read it. The information about GITHUB_TOKEN is not useful and not relevant or even misleading in this case. After I change the read permission, I can execute the command without any issue.