QA » openQA Project

The ISO image is downloaded because it also belongs to the child job, e.g. take a look on the extra_tests_in_textmode scenario that boots a qcow image provided by a parent but the settings specify both ISO and HDD. Having the ISO also does make a difference, e.g. it might be configured to be used as a repo source within openSUSE/SLE. What we can try to do is to override the ISO with ISO= when we do not need it. Or should be try to automatically delete ISO when HDD is specified? Then we would need to still foresee a way to specify an ISO if one really wants to. I favor the first option. Let me see if we can already override ISO in the test settings in https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=yast2_ui_devel&version=Tumbleweed which is in "Development: Tumbleweed" anyway. So I added ISO= in "yast2_ui_devel" in https://openqa.opensuse.org/admin/test_suites and will wait for the next TW snapshot.

EDIT: https://openqa.opensuse.org/tests/1077392#settings still shows the ISO. I assume we need to overwrite with +ISO=. Done that, waiting for next build.

EDIT: 2019-11-13: yast2_ui_devel is nearly never triggered as it relies on yast2_ncurses. Trying with different scenario

openqa-clone-job --skip-chained-deps --within-instance https://openqa.opensuse.org 1083960 _GROUP=0 BUILD= TEST=okurz_poo33946_gnuhealth ISO=

Created job #1084352: opensuse-Tumbleweed-DVD-x86_64-Build20191112-gnuhealth@64bit -> https://openqa.opensuse.org/t1084352

The job passed and cloning that one does only trigger a download of the needed qcow image, no ISO image. I made that change live now on the test suite "gnuhealth".

So I see two independant ways how to continue:

• Somehow make an empty ISO variable the default when an HDD is used -> #59397
• Specify +ISO= on all test suites that do not need the ISO -> #59394