action #124497
Updated by livdywan about 1 year ago
## Observation
openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install+publish@64bit-2G fails in
[openqa_webui](https://openqa.opensuse.org/tests/3118136/modules/openqa_webui/steps/12)
## Test suite description
Maintainer: okurz@suse.de Test for installation of openQA itself. To be used with "openqa" distri. Publishes an qcow2 image including the openQA installation ready to run as an appliance.
## Reproducible
Fails since (at least) Build [:TW.18074](https://openqa.opensuse.org/tests/3117745)
## Expected result
Last good: [:TW.18073](https://openqa.opensuse.org/tests/3117690) (or more recent)
## Acceptance criteria
* **AC1:** No more version conflicts between perl-Mojolicious-Plugin-AssetPack 2.13 and 2.14
## Suggestions
* Identify and fix the version pinning if applicable
* Download Tumbleweed qcow file, run locally with qemu-system…, e.g. `qemu-system-x86_64 -m 4096m -hda my_file.qcow2` or use virt-manager, take a look into the details of `zypper lr --uri` and check for allowVendorChange in zypper config, then try to reproduce manually, inspect RPM files for dependencies and how they came in
* okurz: hm, maybe because we boot an HDD image of the "next-to-be-tested Tumbleweed" which has repos pointing to the openQA Tumbleweed snapshot of today including AssetPack 14 but https://build.opensuse.org/project/repository_state/devel:openQA/openSUSE_Tumbleweed is built against the last release snapshot? Or the other way around?
## Further details
Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=openqa&flavor=dev&machine=64bit-2G&test=openqa_install%2Bpublish&version=Tumbleweed)