openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-01-24T14:09:51ZopenSUSE Project Management Tool
Redmine qe-yam - action #154183 (Rejected): Yam support images not being replaced by latest runshttps://progress.opensuse.org/issues/1541832024-01-24T14:09:51Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>While working on <a href="https://progress.opensuse.org/issues/153043" class="external">poo#153043</a> , the realization that the published images on osd are not replaced by the latest runs of teh yam support images tests occurred. This can be a problem as it invalidates all the effort of minimizing patch time.</p>
<p><strong>Acceptance criteria</strong></p>
<ul>
<li>Make sure that a test publishing an image under the same name can replace an existing one.</li>
<li>Check if the above applies for all archs.</li>
</ul>
<p>Proposal: this can be done by creating a dev job group, publish some images gnome images under a certain name and replace them with textmode images but keeping the same PUBLISH_HDD name and then proceed to see if they where replaced by booting into them (either manually or by using some other openqa test). Any other way of verification would be acceptable as well.</p>
qe-yam - action #133373 (Rejected): Tidy up migration yaml job groups with yamllinthttps://progress.opensuse.org/issues/1333732023-07-26T10:24:05Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>The <a href="https://gitlab.suse.de/coolgw/wegao-test/-/tree/master/JobGroups" class="external">migration job group yamls</a>, if parsed with yamllint, show a lot of errors. It's better to tidy them up and re-order the test suites for each product and architecture according to name alphabetical order, for better readability.</p>
<p>Note: yamllint is available in opensuse repo as python311-yamllint package. Documentation <a href="https://yamllint.readthedocs.io/en/stable/" class="external">here</a></p>
qe-yam - action #132839 (New): Use Mojo race condition where applicable in future testshttps://progress.opensuse.org/issues/1328392023-07-17T07:51:48Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After PR: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17150" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17150</a><br>
for handling the java license popup during installation settings, it was noticed and commended here <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17150#discussion_r1251875831" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17150#discussion_r1251875831</a> <br>
that we can use race conditions. An available library for openqa workers, here: <a href="https://docs.mojolicious.org/Mojo/Promise" class="external">https://docs.mojolicious.org/Mojo/Promise</a><br>
We could start using this after we investigate the functionality and proper syntax. Ask for help, if needed, in slack channel #discuss-perl</p>
<p><strong>Acceptance criteria</strong></p>
<ul>
<li>Research how we can use it in our testing code, make an example by refactoring existing code.</li>
<li>Make a demo for sharing the knowledge.</li>
</ul>
qe-yam - action #124014 (Rejected): Watch for powerpc KVM yast2_nfs_v3/4_server/client if network...https://progress.opensuse.org/issues/1240142023-02-07T09:09:44Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Due to <a href="https://openqa.suse.de/tests/10441871#next_previous" class="external">sporadic failures</a> for ppc64le architecture, the multimachine test yast2_nfs_v3_server/client was moved to development YaST job group. <br>
We should check if the sporadic failures persist, if any action was taken to fix the ppc64le networking issues, and move the test back to YaST job group or remove it completely. </p>
<p>Relevant ticket: <a href="https://progress.opensuse.org/issues/121555" class="external">https://progress.opensuse.org/issues/121555</a> </p>
qe-yam - action #122224 (Resolved): yast2_lan_restart_vlan fails due to change in devices orderhttps://progress.opensuse.org/issues/1222242022-12-20T10:51:40Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>The module yast2_lan_restart_vlan fails when it tries to select vlan0 using needles, as the order of the devices seems to be different than it used to be.The test is expecting vlan0 to be last, so arrows go only downwards, but the device appears first and cannot get highlighted in order for the needle to get matched. We should check if the appearance of the devices shows as expected and modify the test module to be able to select vlan0 even if it doesn't appear last.</p>
<p>See needles:<br>
<a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=yast2_gui&version=15-SP5#step/yast2_lan_restart_vlan/32" class="external">https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=yast2_gui&version=15-SP5#step/yast2_lan_restart_vlan/32</a><br>
and <br>
<a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=yast2_gui&version=15-SP5#step/yast2_lan_restart_vlan/44" class="external">https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=yast2_gui&version=15-SP5#step/yast2_lan_restart_vlan/44</a></p>
<p>It looks like the order is changing while the test tries to get a needle match</p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Ensure selection is performed properly in yast2_lan_restart_vlan</p>
qe-yam - action #102515 (Closed): validate_self_update greps only in /var/log/y2log and misses co...https://progress.opensuse.org/issues/1025152021-11-16T10:52:18Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Online-ppc64le-yast_self_update@ppc64le fails in<br>
<a href="https://openqa.suse.de/tests/7618710/modules/validate_self_update/steps/8" class="external">validate_self_update</a></p>
<p>After checking the y2logs, it seemed as if the self update was skipped. Yast team prompted for a bug report ( see bug#1192515 <a href="https://bugzilla.suse.com/show_bug.cgi?id=1192515">https://bugzilla.suse.com/show_bug.cgi?id=1192515</a> ) where they spotted that in compressed y2log-1 , the self update really happens. We need to investigate why the y2logs for ppc64le can be sporadically compressed (meaning probably that there are more logs during installation) and why there are logs for skipping self update (the following logs are spotted only in case of test failure:</p>
<pre><code>2021-10-29 08:26:00 <1> install(4141) [Ruby] clients/inst_update_installer.rb(installer_updated?):203 /var/lib/YaST2/installer_updated exists
2021-10-29 08:26:00 <1> install(4141) [Ruby] clients/inst_update_installer.rb(main):70 Self update not needed, skipping
2021-10-29 08:26:00 <1> install(4141) [Interpreter] modules/ProductControl.rb:1346 Called YaST client returned.
2021-10-29 08:26:00 <0> install(4141) [Interpreter] modules/ProductControl.rb:1346 Called YaST client returned: `next
2021-10-29 08:26:00 <0> install(4141) [Ruby] modules/Hooks.rb(initialize):156 Creating hook 'after_update_installer' from ''
2021-10-29 08:26:00 <0> install(4141) [Ruby] modules/Hooks.rb(find_hook_files):188 Searching for hook files in '/var/lib/YaST2/hooks/installation'...
2021-10-29 08:26:00 <1> install(4141) [Ruby] modules/Hooks.rb(execute):165 Executing hook 'after_update_installer'
2021-10-29 08:26:00 <1> install(4141) [Ruby] modules/ProductControl.rb(RunFrom):1381 Calling `inst_update_installer ($["enable_back":true, "enable_next":true]) returned `next
</code></pre>
<p>If there is something suspicious, we should update bug#1192515, otherwise we should modify the test module validate_self_update to grep in compressed logs as well (or avoid compressing logs before the module runs, if there is a way).</p>
<p>I have ran the test 10 times here: <a href="https://openqa.suse.de/tests/7675257#next_previous">https://openqa.suse.de/tests/7675257#next_previous</a><br>
The module fails 4/10 , usually for workers in QA-Power8-4-kvm , but that is not a reliable indication because there is one failure for QA-Power8-5-kvm as well and also some tests have passed for QA-Power8-4-kvm workers.</p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Test suite conducts installation with self-update explicitly enabled. No hard checks are done that the self-updating is really disabled. Installation is validated by successful boot and that YaST does not report any issue.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/7618710" class="external">61.1</a> (current job)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/7591796" class="external">58.2</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=ppc64le&distri=sle&flavor=Online&machine=ppc64le&test=yast_self_update&version=15-SP4" class="external">latest</a></p>
qe-yam - action #93032 (Closed): Use accept_license module with libyui-rest-api in all test suite...https://progress.opensuse.org/issues/930322021-05-24T11:03:29Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>There is <code>accept_license</code> module, implemented with LibyuiClient already: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/licensing/accept_license.pm" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/licensing/accept_license.pm</a>. It is already used in <a href="https://openqa.suse.de/tests/5951331" class="external">installer_extended</a> test suite. </p>
<a name="Scope"></a>
<h2 >Scope:<a href="#Scope" class="wiki-anchor">¶</a></h2>
<p>Job Groups: YaST, openSUSE Tumbleweed, openSUSE Leap 15<br>
Test Cases: #1 - Accept license agreement (Please, see test cases in <a href="https://progress.opensuse.org/issues/93282" class="external">https://progress.opensuse.org/issues/93282</a>).</p>
<a name="Task"></a>
<h2 >Task<a href="#Task" class="wiki-anchor">¶</a></h2>
<ol>
<li>Replace the old <code>accept_license</code> module with the new <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/licensing/accept_license.pm" class="external">accept_license</a> module in all the test suites for SLE15-SP3 YaST Job Group;</li>
<li>Adapt existing implementation to be used on Tumbleweed and openSUSE Leap 15 also (i.e. use DistributionFactory to provide the proper controller for TW and Leap, so that the test module remains same, but implementation of <code>get_license_agreement()->accept_license()</code> is different), as on TW and Leap there is no checkbox for accepting License.</li>
<li>Replace the old <code>accept_license</code> module with the new <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/licensing/accept_license.pm" class="external">accept_license</a> module in all the test suites for Tumbleweed and openSUSE Leap 15. </li>
</ol>
<p><strong>Important Notes:</strong><br>
All the cases that do not related to accepting license are out of scope:</p>
<ul>
<li><code>switch_keyboard_gnome/textmode</code> is out of scope and will be implemented in separate ticket, so for now please leave the old 'welcome' module there for such cases;</li>
<li>Product Selection Screen is out of scope, it will be implemented in separate ticket.</li>
</ul>
<p>The new module should replace the old "accept_license" used in SLE, and "welcome" module used in opensuse. It should work for both textmode and graphical installations. Please see identified scenarios in <a class="issue tracker-4 status-5 priority-4 priority-default closed child" title="action: [timeboxed:16h] Define all the test scenarios in welcome and accept_license test modules (Closed)" href="https://progress.opensuse.org/issues/88939">#88939</a> as additional help.</p>
qe-yam - action #91136 (Rejected): Textmode test suite fails for s390x-kvmhttps://progress.opensuse.org/issues/911362021-04-14T13:20:42Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After implementing libyui for the mentioned tests, there is a strange network failure. The url that libyui is trying to connect to seems correct but the app doesn't connect successfully. The failure is the same for all machines:<br>
<a href="https://openqa.suse.de/tests/5814857#step/bootloader_start/30" class="external">https://openqa.suse.de/tests/5814857#step/bootloader_start/30</a> </p>
<p>Similar issue is visible on powerVM: <a class="issue tracker-4 status-5 priority-5 priority-high3 closed" title="action: [timeboxed:16h] libyui REST API cannot be accessed on powerVM (Closed)" href="https://progress.opensuse.org/issues/90776">#90776</a>, so might be that it's same issue for the both backends</p>
qe-yam - action #91130 (Closed): Use libyui for btrfs_libstorage-ng ipmi and zVMhttps://progress.opensuse.org/issues/911302021-04-14T13:15:03Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Currently we are using the old modules for the btrfs_libstorage-ng on the mentioned architectures. The libyui functionality shoudl be working after merging <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12298" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12298</a></p>
<p>For guided partitioning, there need to be additional steps implemented that will choose the disk(s) for the installation.<br>
Module tests/installation/partitioning/guided_setup.pm does not cover this option:<br>
<a href="https://openqa.suse.de/tests/5821208#step/guided_setup/2" class="external">https://openqa.suse.de/tests/5821208#step/guided_setup/2</a></p>
qe-yam - action #89494 (Rejected): Validate editing partition for mount_by optionshttps://progress.opensuse.org/issues/894942021-03-04T12:45:10Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In ticket : <a href="https://progress.opensuse.org/issues/88533" class="external">https://progress.opensuse.org/issues/88533</a> a new test scenario "fstab_mount_by" was implemented , for mount_by option validation after installation. The scenario covers editing the fstab options for new partitions added in the partitioning. </p>
<p>The objective of this follow-up ticket is to extend coverage and perform installation on the image created by "fstab_mount_by" scenario and, while partitioning, edit the existing partitions, check if the existing mount_by option for each partition is recognized correctly by the expert partitioner and validate after installation if the new options take effect correctly.</p>
qe-yam - action #76888 (Closed): Unit test for yast2-metapackage-handler OneClickInstallWorkerFun...https://progress.opensuse.org/issues/768882020-11-02T19:12:01Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Add the following functions to the unit test for OneClickInstallWorkerFunction.rb</p>
<p>InitSlideShow<br>
InstallPackages<br>
InstallPatterns<br>
RemovePackages</p>
<p><a href="https://github.com/yast/yast-metapackage-handler" class="external">https://github.com/yast/yast-metapackage-handler</a></p>
<p>Helpful links:<br>
Builtins <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb</a><br>
Ops <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb</a><br>
deep_copy <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb</a><br>
PackageSlideShow <a href="https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb" class="external">https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb</a><br>
Progress <a href="https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb</a><br>
SlideShow <a href="https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb</a></p>
qe-yam - action #76885 (Resolved): Unit test for yast2-metapackage-handler OneClickInstallWorkerF...https://progress.opensuse.org/issues/768852020-11-02T19:10:38Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Add the following functions to the unit test for <a href="https://github.com/yast/yast-metapackage-handler/blob/master/src/modules/OneClickInstallWorkerFunctions.rb" class="external">OneClickInstallWorkerFunction.rb</a></p>
<p>DeDupe<br>
AddRepositories<br>
RemoveAddedRepositories</p>
<p><a href="https://github.com/yast/yast-metapackage-handler" class="external">https://github.com/yast/yast-metapackage-handler</a></p>
<p>Helpful links:<br>
Builtins <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb</a><br>
Ops <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb</a><br>
deep_copy <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb</a><br>
PackageSlideShow <a href="https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb" class="external">https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb</a><br>
Progress <a href="https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb</a><br>
SlideShow <a href="https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb</a></p>
<p>See previous PRs for progress of unit testing coverage: <a href="https://github.com/yast/yast-metapackage-handler/pull/23" class="external">https://github.com/yast/yast-metapackage-handler/pull/23</a></p>
qe-yam - action #76882 (Resolved): Unit test for yast2-metapackage-handler OneClickInstall.rb (pa...https://progress.opensuse.org/issues/768822020-11-02T19:05:32Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Add the following functions to the unit test for OneClickInstall.rb (<a href="https://github.com/yast/yast-metapackage-handler/blob/master/src/modules/OneClickInstall.rb" class="external">https://github.com/yast/yast-metapackage-handler/blob/master/src/modules/OneClickInstall.rb</a>)</p>
<ul>
<li>Load</li>
<li>makeXMLFriendly</li>
<li>fromXMLFriendly</li>
<li>SetupXML</li>
<li>ToXML</li>
<li>FromXML</li>
</ul>
<p><a href="https://github.com/yast/yast-metapackage-handler" class="external">https://github.com/yast/yast-metapackage-handler</a></p>
<p>Helpful links:<br>
Builtins <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb</a><br>
Ops <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb</a><br>
deep_copy <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb</a><br>
PackageSlideShow <a href="https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb" class="external">https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb</a><br>
Progress <a href="https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb</a><br>
SlideShow <a href="https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb</a></p>
qe-yam - action #76879 (Resolved): Unit test for yast2-metapackage-handler OneClickInstall.rb (pa...https://progress.opensuse.org/issues/768792020-11-02T19:04:32Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Add the following functions to the unit test for OneClickInstall.rb ( <a href="https://github.com/yast/yast-metapackage-handler/blob/master/src/modules/OneClickInstall.rb" class="external">https://github.com/yast/yast-metapackage-handler/blob/master/src/modules/OneClickInstall.rb</a> )</p>
<p>GetRequiredRepositories<br>
GetNonRequiredRepositories<br>
SetNonRequiredRepository<br>
SetRequiredRepositories<br>
GetRequiredSoftware<br>
GetRequiredPackages<br>
GetRequiredPatterns<br>
GetRequiredRemoveSoftware<br>
HaveAnyRecommended</p>
<p><a href="https://github.com/yast/yast-metapackage-handler" class="external">https://github.com/yast/yast-metapackage-handler</a></p>
<p>Helpful links:<br>
Builtins <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb</a><br>
Ops <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb</a><br>
deep_copy <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb</a><br>
PackageSlideShow <a href="https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb" class="external">https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb</a><br>
Progress <a href="https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb</a><br>
SlideShow <a href="https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb</a></p>
openQA Project - action #69313 (Resolved): When using refspec for ppc for a particular job, PRODU...https://progress.opensuse.org/issues/693132020-07-24T10:25:20Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>While attempting to run refspecs for test "autoyast_reinstall" job on various architectures, I faced an issue specifically on ppc64le. The PRODUCTDIR needs to be set manually like following: <br>
<code>openqa-clone-custom-git-refspec https://github.com/sofiasyria/os-autoinst-distri-opensuse/tree/ac68803 https://openqa.suse.de/tests/4427385 ASSET_1="04427383-autoinst.xml" YAML_TEST_DATA=test_data/yast/autoyast_reinstall/autoyast_reinstall_ppc64le-hmc.yaml PRODUCTDIR="os-autoinst-distri-opensuse/products/sle"</code></p>
<p>If the above command is used without the PRODUCTDIR specification, the variable gets the value "os-autoinst-distri-opensuseos-autoinst-distri-opensuse/products/sle" which leads to test failure as here:<br>
<a href="https://openqa.suse.de/tests/4482090" class="external">https://openqa.suse.de/tests/4482090</a></p>
<p>The particular test suite runs for ppc64le-2g, ppc64le-hmc-single-disk, 64bit, s390x and aarch64. For both the ppc machines, the PRODUCTDIR needs to be set manually. For rest of them, it's not necessary.</p>
<p>I have unsuccessfully tried to reproduce the issue with other jobs on ppc.</p>