action #77008
Conduct openQA-in-openQA test on the latest *published* TW snapshot
0%
Description
problem¶
So far the openQA-in-openQA test is conducted on the latest TW snapshot. However, the packages from devel:openQA like os-autoinst are built against the latest published TW snapshot and therefore might require a lower version of certain dependencies. For instance, currently the openQA-in-openQA test is failing because libopencv_core.so.4.4 is required by os-autoinst but the used TW snapshot is already at libopencv_core.so.4.5 (see https://openqa.opensuse.org/tests/1460442#step/openqa_worker/7).
acceptance criteria¶
- AC1: The openQA-in-openQA test is conducted on the latest published TW snapshot
suggestions¶
- Checkout the code responsible for finding the latest TW image: https://github.com/os-autoinst/scripts/blob/master/trigger-openqa_in_openqa#L25
- To number of the latest published snapshot could be looked up from openQA tags created by the
ttmbot: https://openqa.opensuse.org/group_overview/1.json
History
#1
Updated by mkittler 3 months ago
Updated by Seems like the build number is actually already determined within the function mentioned in the first suggestion. It comes from the $BUILD_TAG variable which is set by Jenkins. The function actually just determines the name of the corresponding qcow image. Maybe it makes more sense to implement this where $BUILD_TAG is set - but where is that?
#3
Updated by okurz 3 months ago
Updated by - Category set to Concrete Bugs
- Target version set to Ready
BUILD_TAG is only used in https://github.com/os-autoinst/scripts/blob/master/trigger-openqa_in_openqa#L34 and I don't see the relation. As you described yourself it is set by jenkins and used to set a build within openQA. You shouldn't be concerned about that.
#5
Updated by mkittler 3 months ago
- Status changed from Workable to In Progress
BUILD_TAG is only used in…
That's not true because the other variable $build is initialized from it in that line and is later passed as BUILD in the isos post call. But you're right, this build has still nothing to do with the TW build which we're using.
#6
Updated by mkittler 2 months ago
- Status changed from In Progress to Resolved
I fixed the installation on the Jenkins host, it seems to work now:
+ find_latest_published_tumbleweed_image
++ curl https://openqa.opensuse.org/group_overview/1.json
++ jq -r '[.build_results[] | select(.tag.description=="published") | select(.version=="Tumbleweed") | .build] | sort | reverse | .[0]'
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
100 8503 100 8503 0 0 5357 0 0:00:01 0:00:01 --:--:-- 5354
100 8503 100 8503 0 0 5354 0 0:00:01 0:00:01 --:--:-- 5354
+ latest_published_tw_build=20201110
+ [[ -n 20201110 ]]
++ /usr/share/openqa/script/openqa-cli api --host https://openqa.opensuse.org assets get
++ jq -r '[.assets[] | select(.name | test("Tumbleweed-x86_64-20201110-Tumbleweed\\@64bit.qcow"))] | .[0] | .name'
+ qcow=opensuse-Tumbleweed-x86_64-20201110-Tumbleweed@64bit.qcow2
+ [[ -n opensuse-Tumbleweed-x86_64-20201110-Tumbleweed@64bit.qcow2 ]]
+ '[' https://openqa.opensuse.org '!=' https://openqa.opensuse.org ']'
++ echo jenkins-trigger-openQA_in_openQA-TW-6333
++ sed -e s/jenkins-trigger-openQA_in_openQA-/:/ -e s/-/./g
+ build=:TW.6333
+ trigger
+ '[' openqa.opensuse.org = openqa.opensuse.org ']'
+ ARGS=OPENQA_HOST=http://openqa.opensuse.org
+ /usr/share/openqa/script/client --host https://openqa.opensuse.org isos post VERSION=Tumbleweed DISTRI=openQA FLAVOR=dev BUILD=:TW.6333 ARCH=x86_64 BACKEND=qemu WORKER_CLASS=qemu_x86_64 HDD_1=opensuse-Tumbleweed-x86_64-20201110-Tumbleweed@64bit.qcow2
#7
Updated by cdywan 22 days ago
Updated by FYI the PR fixing this ticket was: https://github.com/os-autoinst/scripts/pull/42
I stumbled onto this change whilst investigating #81492 and trying to asses the intention of the code.