coordination #58184: [saga][epic][use case] full version control awareness within openQA, e.g. user forks and branches, fully versioned test schedules and configuration settings
coordination #80372: [epic] Cleanup vars.json as initial information container between openQA worker and isotovideo
coordination #67723: [epic] Remote openQA worker fails to run tests from openqa-clone-custom-git-refspec
Remote openQA worker fails to run tests from openqa-clone-custom-git-refspec due to differing paths
See the original issue in #67723 for details:
Remote openQA worker fails to run tests from
openqa-clone-custom-git-refspec, see: https://openqa.opensuse.org/tests/1287895
[0mneedles_dir not found: /var/lib/openqa/pool/2/os-autoinst-distri-opensuse/var/lib/openqa/cache/openqa1-opensuse/tests/opensuse/products/opensuse/needles (check vars.json?) at /usr/lib/os-autoinst/needle.pm line 330, <$fh> line 20. [37m[2020-06-04T09:10:50.934 UTC] [debug] terminating command server 19004 because test execution ended through exception [0m[37m[2020-06-04T09:10:51.935 UTC] [debug] done with command server [0m18926: EXIT 1
- AC1: openqa-clone-custom-git-refspec creates jobs with valid CASEDIR and valid NEEDLES_DIR if source job is a "remote worker"
- AC2: openqa-clone-custom-git-refspec still creates jobs that find tests from specified git hash and needles for other workers
#7 Updated by Xiaojing_liu about 1 year ago
I did a test following this comment: https://progress.opensuse.org/issues/67723#note-12 on o3.
barry:~/:# openqa-clone-custom-git-refspec https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12349 https://openqa.opensuse.org/tests/1701892 WORKER_CLASS=aws Created job #1706385: opensuse-15.3-DVD-aarch64-Build134.1-kde@aarch64 -> https://openqa.opensuse.org/t1706385
The source job
1701892 was run on worker
openqa-aarch64:2. This worker is enabled cache service and using a relative path. The cloned job is run on
ip-172-25-5-39:2, and the setting
I also did a test in my local: http://10.67.19.157/tests/531. This new job is run on a local worker that isn't enabled cache. The source job http://10.67.19.157/tests/530 was run on a remote worker which is enabled cache service. Both of the workers are enabled relative path.
So could we consider this remote worker issue has been fixed?