openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-01-17T08:59:42ZopenSUSE Project Management Tool
Redmine ALP - action #153760 (Resolved): [qe-core]Adapt svirt backend to be able to boot systems with roo...https://progress.opensuse.org/issues/1537602024-01-17T08:59:42Zjlausuchjalausuch@suse.com
<p>ALP images (following Factory approach) do not allow root ssh by default, the best practices are to use a key-pair to ssh to the system.</p>
<p>There is a way to enable it, which consists of installing the package <code>openssh-server-config-rootlogin</code>, which is simply doing <code>echo 'PermitRootLogin yes' >> /etc/sshd/sshd_config.d/root_login_config.</code>.</p>
<p>Our svirt backend rely on doing a root ssh to the machine after it's booted, therefore it fails to do so.</p>
<p>There are several ideas to workaround this:<br>
1) Add <code>echo 'PermitRootLogin yes' >> /etc/sshd/sshd_config.d/root_login_config >$pty</code> to the svirt backend commands. <br>
2) Create a keypair for each run and inject it to the VM using svirt backend commands. <br>
3) Create new combustion script for s390x including the command `echo 'PermitRootLogin yes' >> /etc/sshd/sshd_config.d/root_login_config</p>
<a name="Acceptance-criteria"></a>
<h3 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h3>
<ul>
<li>ALP s390x images boot with svirt backend</li>
</ul>
ALP - action #114935 (Resolved): Add standard container host tests for ALP prototype in O3https://progress.opensuse.org/issues/1149352022-08-03T07:39:42Zjlausuchjalausuch@suse.com
<p>There are currently no container tests for ALP prototype.</p>
<p>The idea is to enable the same set of tests that are run for MicroOS/Leap-Micro, e.g. <a href="https://openqa.opensuse.org/tests/2433988" class="external">https://openqa.opensuse.org/tests/2433988</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria:<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<p>Create a new jobs <code>alp_containers</code> for the flavors <code>kvm-and-xen</code> and <code>kvm-and-xen_NonTransactional</code> which schedules the following modules:</p>
<pre><code>- toolbox
- podman
- image_podman
- podman_3rd_party_images
- podman_pods
- rootless_podman
</code></pre> ALP - action #112424 (Resolved): 4. Enable OBS sync for ALP images for openQAhttps://progress.opensuse.org/issues/1124242022-06-14T16:06:33Zjlausuchjalausuch@suse.com
<p>To be able to trigger new openQA test for every build of ALP images, we need to enable this configuration into <a href="https://github.com/os-autoinst/openqa-trigger-from-obs" class="external">https://github.com/os-autoinst/openqa-trigger-from-obs</a>.</p>
<p>The OBS project to sync is: <code>devel:LEO/ALP</code>: <a href="https://build.opensuse.org/package/show/devel:LEO/ALP" class="external">https://build.opensuse.org/package/show/devel:LEO/ALP</a><br>
The images are available for download here: <a href="https://download.opensuse.org/repositories/devel:/LEO/images/" class="external">https://download.opensuse.org/repositories/devel:/LEO/images/</a><br>
We need to sync the following flavors (for now):</p>
<ul>
<li>kvm-and-xen</li>
<li>kvm-and-xen_NonTransactional</li>
<li>SelfInstall</li>
<li>SelfInstall_NonTransactional</li>
</ul>
<p>and also sync the repository so that we can use the <code>SCC_URL</code> variable pointing to local assets.</p>
openQA Project - action #110566 (Resolved): [tools] Problem with ISOS Post command from OBS synchttps://progress.opensuse.org/issues/1105662022-05-03T09:57:28Zjlausuchjalausuch@suse.com
<p>The latest OSD 15-SP4 JeOS (Minimal-VM) jobs have only been triggered for Raspbery-Pi flavor:<br>
This is the OBS sync log: <a href="https://openqa.suse.de/admin/obs_rsync/SUSE:SLE-15-SP4:GA:TEST%7Cjeos/runs/.run_last/download/openqa.cmd.log" class="external">https://openqa.suse.de/admin/obs_rsync/SUSE:SLE-15-SP4:GA:TEST%7Cjeos/runs/.run_last/download/openqa.cmd.log</a></p>
<p>Looking at the product scheduled:<br>
<a href="https://openqa.suse.de/admin/productlog?id=910513" class="external">https://openqa.suse.de/admin/productlog?id=910513</a></p>
<pre><code>Results
{
"failed_job_info": [],
"successful_job_ids": [
8676719,
8676726,
8676732,
8676735,
8676742,
8676748,
8676753,
8676758
]
}
</code></pre>
<p>this is what I would expect from other isos post, but for instance:<br>
<a href="https://openqa.suse.de/admin/productlog?id=910516" class="external">https://openqa.suse.de/admin/productlog?id=910516</a> or <br>
<a href="https://openqa.suse.de/admin/productlog?id=910515" class="external">https://openqa.suse.de/admin/productlog?id=910515</a><br>
have empty results:</p>
<pre><code>Results
No results available.
</code></pre>
<p>and the jobs were not scheduled at all. </p>
openQA Tests - action #109046 (Resolved): [tools] auto_review:"Unable to find image SLES15-SP3-Je...https://progress.opensuse.org/issues/1090462022-03-28T06:23:08Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Migration-from-SLE12-SPx-s390x-offline_sles12sp3_ltss_pscc_asmm-lgm_all_full@s390x-kvm-sle15 fails in<br>
<a href="https://openqa.suse.de/tests/8415599/modules/bootloader_zkvm/steps/18" class="external">bootloader_zkvm</a><br>
But the qcow exists:</p>
<pre><code>$ /var/lib/openqa/share/factory/hdd/fixed> ll SLES-12-SP3-s390x-GM-gnome-allpatterns.qcow2
-rw-r--r-- 1 geekotest nogroup 14485946368 Jan 14 08:45 SLES-12-SP3-s390x-GM-gnome-allpatterns.qcow2
</code></pre>
<p>And the asset is actually there:<br>
<img src="https://progress.opensuse.org/attachments/download/13001/hdd.png" alt="" loading="lazy" /></p>
<p>It happens in all jobs with <code>svirt</code> backend that have their HDD in fixed directory. So, all s390x jobs and some others that use that backend too:<br>
Examples:<br>
<a href="https://openqa.suse.de/tests/8414273" class="external">https://openqa.suse.de/tests/8414273</a><br>
<a href="https://openqa.suse.de/tests/8414268" class="external">https://openqa.suse.de/tests/8414268</a><br>
<a href="https://openqa.suse.de/tests/8414272" class="external">https://openqa.suse.de/tests/8414272</a><br>
<a href="https://openqa.suse.de/tests/8414267" class="external">https://openqa.suse.de/tests/8414267</a><br>
<a href="https://openqa.suse.de/tests/8414271" class="external">https://openqa.suse.de/tests/8414271</a><br>
<a href="https://openqa.suse.de/tests/8414266" class="external">https://openqa.suse.de/tests/8414266</a><br>
<a href="https://openqa.suse.de/tests/8414270" class="external">https://openqa.suse.de/tests/8414270</a><br>
<a href="https://openqa.suse.de/tests/8414265" class="external">https://openqa.suse.de/tests/8414265</a><br>
<a href="https://openqa.suse.de/tests/8414269" class="external">https://openqa.suse.de/tests/8414269</a><br>
<a href="https://openqa.suse.de/tests/8414264" class="external">https://openqa.suse.de/tests/8414264</a></p>
<p><a href="https://openqa.suse.de/tests/8414323" class="external">https://openqa.suse.de/tests/8414323</a><br>
<a href="https://openqa.suse.de/tests/8414322" class="external">https://openqa.suse.de/tests/8414322</a><br>
<a href="https://openqa.suse.de/tests/8414321" class="external">https://openqa.suse.de/tests/8414321</a><br>
<a href="https://openqa.suse.de/tests/8414320" class="external">https://openqa.suse.de/tests/8414320</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>The base test suite is used for job templates defined in YAML documents. It has no settings of its own.</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/8345312" class="external">113.1</a></p>
<p>Find jobs referencing this ticket with the help of<br>
<a href="https://raw.githubusercontent.com/os-autoinst/scripts/master/openqa-query-for-job-label" class="external">https://raw.githubusercontent.com/os-autoinst/scripts/master/openqa-query-for-job-label</a> ,<br>
call <code>openqa-query-for-job-label poo#109046</code></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/8292036" class="external">108.1</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=s390x&distri=sle&flavor=Migration-from-SLE12-SPx&machine=s390x-kvm-sle15&test=offline_sles12sp3_ltss_pscc_asmm-lgm_all_full&version=15-SP4" class="external">latest</a></p>
openQA Tests - action #108953 (Resolved): [tools] Performance issues in some s390 workershttps://progress.opensuse.org/issues/1089532022-03-25T07:13:32Zjlausuchjalausuch@suse.com
<p>This ticket is to collect examples of jobs that are failing due to some performance degradation, specially s390x workers.</p>
<p>Installation jobs:<br>
(some of these issues seem to be a slow key press so it doesn't reach the target needle on time):</p>
<ul>
<li><a href="https://openqa.suse.de/tests/8390044#step/select_patterns/5" class="external">https://openqa.suse.de/tests/8390044#step/select_patterns/5</a> - grenache-1:47</li>
<li><a href="https://openqa.suse.de/tests/8387127#step/disable_grub_timeout/18" class="external">https://openqa.suse.de/tests/8387127#step/disable_grub_timeout/18</a> - grenache-1:32</li>
<li><a href="https://openqa.suse.de/tests/8380005#step/add_update_test_repo/38" class="external">https://openqa.suse.de/tests/8380005#step/add_update_test_repo/38</a> - grenache-1:49
<a href="https://openqa.suse.de/tests/8380706#step/add_update_test_repo/10" class="external">https://openqa.suse.de/tests/8380706#step/add_update_test_repo/10</a> - grenache-1:49 </li>
<li><a href="https://openqa.suse.de/tests/8380553#step/cleanup_before_shutdown/4" class="external">https://openqa.suse.de/tests/8380553#step/cleanup_before_shutdown/4</a> (command 'rm -f /etc/udev/rules.d/70-persistent-net.rules' timed out ) - grenache-1:37</li>
</ul>
<p>Other jobs:</p>
<ul>
<li><a href="https://openqa.suse.de/tests/8387144#step/install_updates/14" class="external">https://openqa.suse.de/tests/8387144#step/install_updates/14</a> (command 'rm /tmp/journal_before' timed out) - grenache-1:44</li>
<li><a href="https://openqa.suse.de/tests/8387142#step/image_checks/13" class="external">https://openqa.suse.de/tests/8387142#step/image_checks/13</a> (script timeout: cat /usr/share/combustion-welcome) - grenache-1:33 </li>
</ul>
<p>Boot failures:</p>
<ul>
<li><a href="https://openqa.suse.de/tests/8380156#step/bootloader_zkvm/23" class="external">https://openqa.suse.de/tests/8380156#step/bootloader_zkvm/23</a></li>
<li><a href="https://openqa.suse.de/tests/8380915#step/bootloader_zkvm/22" class="external">https://openqa.suse.de/tests/8380915#step/bootloader_zkvm/22</a></li>
</ul>
openQA Project - action #108824 (Resolved): Some of the daily aggregate tests are cancelled witho...https://progress.opensuse.org/issues/1088242022-03-24T07:02:27Zjlausuchjalausuch@suse.com
<p>Some of the tests that are triggered by the bot-ng are cancelled without any apparent reason and missing logs.</p>
<p>Examples:<br>
<a href="https://openqa.suse.de/tests/8379473" class="external">https://openqa.suse.de/tests/8379473</a><br>
<a href="https://openqa.suse.de/tests/8379476" class="external">https://openqa.suse.de/tests/8379476</a></p>
<p>I have observed this a few times in past days, but I thought it was a sporadic error.<br>
Let's use this ticket to collect these kind of failures.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong>: It is clear what the expected scheduling behavior is (e.g. is VERSION <em>supposed</em> to be 5.1 in the job despite VERSION 5.0 being specified when scheduling the product)</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Clarify with the author of the test - this test is very new
<ul>
<li>Initial hypothesis: Have these jobs <em>not</em> been scheduled by bot-ng?</li>
<li>Find a way to distinguish bot jobs better</li>
<li>Find out why affected jobs are scheduled with 5.0 but show VERSION 5.1 in the settings</li>
</ul></li>
<li><a href="https://gitlab.suse.de/qac/qac-openqa-yaml/-/blob/master/sle-micro/updates.yaml#L170" class="external">https://gitlab.suse.de/qac/qac-openqa-yaml/-/blob/master/sle-micro/updates.yaml#L170</a>
<ul>
<li>Examine bot-ng logs for scheduling the sle-micro, look for both 5.0 and 5.1 versions (the other one could obsolete the first one)</li>
<li>Product log for 5.0 scheduling: <a href="https://openqa.suse.de/admin/productlog?id=886973" class="external">https://openqa.suse.de/admin/productlog?id=886973</a></li>
<li>Product log for 5.1 scheduling: <a href="https://openqa.suse.de/admin/productlog?id=886978" class="external">https://openqa.suse.de/admin/productlog?id=886978</a></li>
</ul></li>
<li>If the bot cancells jobs as expected, comment "Cancelled because of job #foo" on relevant jobs</li>
</ul>
openQA Project - action #103791 (Resolved): After module failure, the console is broken size:Mhttps://progress.opensuse.org/issues/1037912021-12-09T21:37:15Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>I have observed some situations when a module fails and openQA runs the next one, the very first command fails or times out.<br>
Example:</p>
<p>In <a href="https://openqa.suse.de/tests/7806676#step/cifs/4" class="external">this job</a>, after docker_compose failure, the following modules fail in the beginning.</p>
<p>More occurrences:<br>
<a href="https://openqa.suse.de/tests/7806630#step/libvorbis/4" class="external">https://openqa.suse.de/tests/7806630#step/libvorbis/4</a><br>
<a href="https://openqa.suse.de/tests/7810193#step/verify_default_target/4" class="external">https://openqa.suse.de/tests/7810193#step/verify_default_target/4</a></p>
<p>Related Slack thread: <a href="https://suse.slack.com/archives/C02CANHLANP/p1639048127294800" class="external">https://suse.slack.com/archives/C02CANHLANP/p1639048127294800</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong>: Better information exists about the state of the system after loading snapshots or in case of failures</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Add a box to the test module that a snapshot was loaded and since the previous module failed it might affect the result e.g. due to I/O or the system clock being askew</li>
<li>After loading snapshots in os-autoinst use QEMU monitoring commands to find out whether the system is just busy/slow, see <a href="https://qemu-project.gitlab.io/qemu/system/monitor.html" class="external">https://qemu-project.gitlab.io/qemu/system/monitor.html</a> , e.g. "info status" and check if the system is just very busy or responsive. Other commands okurz recommends "info migrate" as we just load a snapshot before, maybe it's not completely finished? Maybe "info dirty_rate" shows if stuff needs to be handled before the system is properly responsive again?</li>
<li>The output of those commands could be used in simple debug log lines, so nothing more fancy required</li>
<li>Try to reproduce with a synthetic setup, could e.g. be part of the os-autoinst full-stack test</li>
</ul>
openQA Tests - action #93339 (Resolved): test fails in validate_btrfshttps://progress.opensuse.org/issues/933392021-06-01T09:16:42Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-Server-DVD-Updates-x86_64-sle_image_on_sle_host@64bit fails in<br>
<a href="https://openqa.suse.de/tests/6149331/modules/validate_btrfs/steps/39" class="external">validate_btrfs</a><br>
Other failures:<br>
All Container jobs, e.g. <a href="https://openqa.suse.de/tests/6151606" class="external">https://openqa.suse.de/tests/6151606</a><br>
All Public Cloud jobs, e.g. <a href="https://openqa.suse.de/tests/6149926#step/validate_btrfs/39" class="external">https://openqa.suse.de/tests/6149926#step/validate_btrfs/39</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>The base test suite is used for job templates defined in YAML documents. It has no settings of its own.</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/6149331" class="external">20210601-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: (unknown) (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=x86_64&distri=sle&flavor=Server-DVD-Updates&machine=64bit&test=sle_image_on_sle_host&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #89287 (Resolved): test fails in yast2_lanhttps://progress.opensuse.org/issues/892872021-03-01T14:48:17Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-JeOS-for-MS-HyperV-x86_64-jeos-main@svirt-hyperv fails in<br>
<a href="https://openqa.suse.de/tests/5552124/modules/yast2_lan/steps/21" class="external">yast2_lan</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<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/5462492" class="external">23.32</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: (unknown) (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=x86_64&distri=sle&flavor=JeOS-for-MS-HyperV&machine=svirt-hyperv&test=jeos-main&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #64724 (Resolved): [kernel][xfstests] Parted fails to create a partitionhttps://progress.opensuse.org/issues/647242020-03-22T18:31:09Zjlausuchjalausuch@suse.com
<p><a href="https://openqa.suse.de/tests/4017525#step/partition/13" class="external">https://openqa.suse.de/tests/4017525#step/partition/13</a></p>
<pre><code>parted /dev/vdb --script -- mklabel gpt
Error: partition(s) on /dev/vdb are being used.
</code></pre> openQA Tests - action #58220 (Resolved): [kernel] fadump LVM test failshttps://progress.opensuse.org/issues/582202019-10-15T20:25:44Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Failure when going into grub screen<br>
<a href="https://openqa.suse.de/tests/3479900#step/kdump_and_crash/64" class="external">grub screen</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: Petr Cervinka <a href="mailto:pcervinka@suse.com">pcervinka@suse.com</a></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/3479900" class="external">0358</a><br>
But it also failed in some <a href="https://openqa.suse.de/tests/3395111" class="external">older run</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>This is an example of <a href="https://openqa.suse.de/tests/3470330#step/kdump_and_crash/64" class="external">successful run</a> in the previous build.</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
openQA Tests - action #58148 (Rejected): [kernel][multipath] Timeout in qa_kernel_multipathhttps://progress.opensuse.org/issues/581482019-10-14T15:19:53Zjlausuchjalausuch@suse.com
<p>The test times out after 2 hours. Need to investigate why.</p>
<p><a href="https://openqa.suse.de/tests/3470142" class="external">https://openqa.suse.de/tests/3470142</a><br>
<a href="https://openqa.suse.de/tests/3470021" class="external">https://openqa.suse.de/tests/3470021</a></p>
openQA Project - action #40415 (Resolved): Concurrent jobs with dependencies don't work if they a...https://progress.opensuse.org/issues/404152018-08-29T11:44:49Zjlausuchjalausuch@suse.com
<a name="Reproducibility"></a>
<h1 >Reproducibility:<a href="#Reproducibility" class="wiki-anchor">¶</a></h1>
<p>We have 2 jobs, let's say PARENT and CHILD, where CHILD has PARALLEL_WITH=PARENT.</p>
<p>I have created 2 tests that are on the same machine "64bit", qemu with some other options:<br>
<a href="http://fromm.arch.suse.de/tests/1394" class="external">http://fromm.arch.suse.de/tests/1394</a><br>
<a href="http://fromm.arch.suse.de/tests/1395" class="external">http://fromm.arch.suse.de/tests/1395</a></p>
<p>The parent job needs the child ID for the mutex command:</p>
<pre><code>my $children = get_children();
my $child_id = (keys %$children)[0];
...
script_run("echo Waiting for child with child_id=$child_id");
mutex_wait("child_ready", $child_id);
</code></pre>
<p>This is one line of the parent's output:</p>
<pre><code>Waiting for child with child_id=1399
</code></pre>
<p>Everything OK so far. CHILD recognizes PARENT as its parent and locking api works without problems.</p>
<p>Then, I have created another machine "64bit-other" with the exact same characteristics as the other one. <a href="http://fromm.arch.suse.de/admin/machines" class="external">http://fromm.arch.suse.de/admin/machines</a><br>
And assign CHILD to "64bit-other" in the job group. </p>
<p>The result is that CHILD doesn't have the parent job in the settings panel any more, and the PARENT's output is now:</p>
<pre><code>Waiting for child with child_id=
</code></pre>
<p>Therefore, the command </p>
<pre><code>mutex_wait("child_ready", $child_id);
</code></pre>
<p>waits forever.</p>
<p>Why having different machines? Well, for virtual jobs it doesn't make sense, but for BareMetal jobs like NFV and InfiniBand tests we are using different workers and machines:<br>
ipmi-sonic and ipmi-tails with different worker classes: 64bit-mlx_con5_sonic and 64bit-mlx_con5_tails respectively. </p>
openQA Project - action #31417 (Rejected): Add support for SSH from Host to VMhttps://progress.opensuse.org/issues/314172018-02-06T14:21:54Zjlausuchjalausuch@suse.com
<p>The VMs that OpenQA launches have an internal IP that is not reachable from the Host. Therefore, there is no way to SSH into them, only VNC is available. </p>
<p>The problem of VNC is that it limits the user comfort when debugging. SSH allows much better experience as you can use your own console and use SCP, bidireccional copy/paste, mouse scrolling, etc. </p>
<p>However, it is possible to SSH from the VM to the Host, therefore Reverse SSH can be used, but it is just a workaround. Having ssh supported directly from the Host would be more convenient.</p>
<p>I think this could be achieved by changing the qemu command line to launch the VM adding a parameter <em>-net user,hostfwd=tcp::7777-:8001</em><br>
Not sure if this is the right place, but it could help to look at this line: <a href="https://github.com/os-autoinst/os-autoinst/blob/master/backend/qemu.pm#L581" class="external">https://github.com/os-autoinst/os-autoinst/blob/master/backend/qemu.pm#L581</a></p>