openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-02-17T11:44:22ZopenSUSE Project Management Tool
Redmine openSUSE admin - tickets #124727 (Closed): Progress APIhttps://progress.opensuse.org/issues/1247272023-02-17T11:44:22Zilausuchilausuch@suse.com
<p>Hi,</p>
<p>I am engineer at SUSE at the department of QE. I am working in a project that extracts information from the progress using the API to generate metrics. It usually do several requests (for the project I am testing >400) in a sort period of time.</p>
<p>I think my IP was blocked because using different VPNs IPs I can continue calling to the API and continue my work. I checked that should be some sort of limitation of number of queries I could perform or request to the machine. I hope that in the future this project will be working in a production environment with different projects.</p>
<p>Is there anyway to solve this situation? And prevent that when we have the system in production will be blocked?</p>
<p>The project is this one:<br>
<a href="https://github.com/ilausuch/project_management_statistics" class="external">https://github.com/ilausuch/project_management_statistics</a><br>
This is also a Hackweek project.</p>
<p>I put in copy to my manager in case you need to ask him about some authorisation. He knows what is objective of this project</p>
<p>Thank you<br>
Best regards,</p>
openSUSE admin - tickets #124559 (Closed): Banned ip for progress?https://progress.opensuse.org/issues/1245592023-02-15T10:01:47Zilausuchilausuch@suse.com
<p>Hi,</p>
<p>I have problems to connect to progress if I use the IP that my ISP give to me (185.234.246.104 ). I have timeouts. The ISP doesn’t change the IP neither if I restart the router, but I can use progress with a public VPN. But it will be better to have access to progress with my IP.</p>
<p>I having using the progress API a lot because I am doing a project that requires querying. Maybe I raised some kind of limit.</p>
<p>Thank you<br>
Best regards</p>
openQA Tests - action #120924 (New): test fails in check_registercloudguest - repository list emptyhttps://progress.opensuse.org/issues/1209242022-11-24T13:05:42Zilausuchilausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-12-SP5-AZURE-Basic-Updates-x86_64-publiccloud_consoletests@64bit fails in<br>
<a href="https://openqa.suse.de/tests/10031130/modules/check_registercloudguest/steps/17" class="external">check_registercloudguest</a></p>
<p>This should be esporadic, but we have a check that fails on <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/50513d2aeb2a693e8c2742d6d7902da3dc8a539e/tests/publiccloud/check_registercloudguest.pm#L50" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/50513d2aeb2a693e8c2742d6d7902da3dc8a539e/tests/publiccloud/check_registercloudguest.pm#L50</a></p>
<pre><code class="text syntaxhl" data-language="text">timeout 360 ssh -i '/root/.ssh/id_rsa' "azureuser@xxxx" -- 'sudo zypper lr | wc -l'
</code></pre>
<p>The problem is that there is an output, so all this line works fine</p>
<p>An other case: <a href="https://openqa.suse.de/tests/10033543/logfile?filename=serial_terminal.txt" class="external">https://openqa.suse.de/tests/10033543/logfile?filename=serial_terminal.txt</a></p>
<pre><code class="text syntaxhl" data-language="text">Warning: No repositories defined.
</code></pre>
<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/10024236" class="external">20221123-1</a></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/10016909" class="external">20221122-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=x86_64&distri=sle&flavor=AZURE-Basic-Updates&machine=64bit&test=publiccloud_consoletests&version=12-SP5" class="external">latest</a></p>
openQA Tests - action #102948 (New): test fails in podman_3rd_party_images - Waiting for Godot: p...https://progress.opensuse.org/issues/1029482021-11-24T10:57:46Zilausuchilausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-EC2-BYOS-Updates-x86_64-publiccloud_containers@64bit fails in<br>
<a href="https://openqa.suse.de/tests/7731431/modules/podman_3rd_party_images/steps/716" class="external">podman_3rd_party_images</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/7710839" class="external">20211121-1</a></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/7707128" class="external">20211120-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=x86_64&distri=sle&flavor=EC2-BYOS-Updates&machine=64bit&test=publiccloud_containers&version=15-SP3" class="external">latest</a></p>
openQA Project - action #91046 (Resolved): CI: "webui-docker-compose" seems that eventually fails...https://progress.opensuse.org/issues/910462021-04-13T09:08:23Zilausuchilausuch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>In <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: containers: The deploy using docker-compose is not stable and eventually fails (Resolved)" href="https://progress.opensuse.org/issues/89731">#89731</a> we introduced a initial webui container in charge of initializing the database. We have a test where the health check failed<br>
<a href="https://github.com/os-autoinst/openQA/pull/3838/checks?check_run_id=2329551052" class="external">https://github.com/os-autoinst/openQA/pull/3838/checks?check_run_id=2329551052</a></p>
<p>The problem is that the docker-compose exit with an error because the health check of the webuid_db_init container failed</p>
<pre><code class="text syntaxhl" data-language="text"> Name Command State Ports
------------------------------------------------------------------------------------------------------------------------------------------------
webui_db_1 docker-entrypoint.sh postgres Up (healthy) 5432/tcp
webui_webui_db_init_1 sh -c chmod -R a+rwX /data ... Up (unhealthy) 443/tcp, 80/tcp, 0.0.0.0:49153->9526/tcp, 9527/tcp, 9528/tcp, 9529/tcp
make: *** [Makefile:306: test-containers-compose] Error 1
</code></pre>
<p>The healthcheck is this one <br>
<a href="https://github.com/os-autoinst/openQA/blob/abd9a2297430377cd9876c3cbcec8b2cb4302722/container/webui/docker-compose.yaml#L116" class="external">https://github.com/os-autoinst/openQA/blob/abd9a2297430377cd9876c3cbcec8b2cb4302722/container/webui/docker-compose.yaml#L116</a></p>
<p>Take in consideration the DB error lines</p>
<pre><code class="text syntaxhl" data-language="text">db_1 | 2021-04-13 02:43:08.038 UTC [98] ERROR: relation "api_keys" does not exist at character 15
db_1 | 2021-04-13 02:43:08.038 UTC [98] STATEMENT: select * from api_keys;
db_1 | 2021-04-13 02:43:10.441 UTC [100] ERROR: relation "dbix_class_deploymenthandler_versions" does not exist at character 24
db_1 | 2021-04-13 02:43:10.441 UTC [100] STATEMENT: SELECT me.version FROM dbix_class_deploymenthandler_versions me ORDER BY id DESC LIMIT $1
db_1 | 2021-04-13 02:43:10.446 UTC [100] ERROR: relation "dbix_class_deploymenthandler_versions" does not exist at character 24
</code></pre>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC 1</strong>: Determine the cause of the failure</li>
<li><strong>AC 2</strong>: Fix the problem</li>
</ul>
openQA Project - action #90989 (Workable): containers: Configurable workdir location in docker-co...https://progress.opensuse.org/issues/909892021-04-12T09:55:25Zilausuchilausuch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Currently, the workdir is created in the <code>containers/webui</code> directory with two problems:</p>
<ul>
<li>This clutters the git directory. (The path is already in <code>.gitignore</code>, though.)</li>
<li>The directory is owned by root causing the tidy script to fail on permission errors.</li>
</ul>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong>: Use a different default directory or at least prevent the interference with the tidy script.</li>
<li><strong>AC2</strong>: Allow to configure the workdir path, e.g. via an environment variable.</li>
<li><strong>AC3</strong>: Document where files are stored by default and AC2.</li>
</ul>
openQA Project - action #89929 (New): containers: Fix nginx configuration to independence the WS ...https://progress.opensuse.org/issues/899292021-03-11T12:17:32Zilausuchilausuch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Now the configuration of nginx uses the following urls as backend for websockets and livehandler</p>
<ul>
<li><a href="http://webui_websockets_1:9527" class="external">http://webui_websockets_1:9527</a>;</li>
<li><a href="http://webui_livehandler_1:9528" class="external">http://webui_livehandler_1:9528</a>;</li>
</ul>
<p>The problem is that this name (webui_...) is dependent on the parent directory of the docker-compose</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC 1</strong>: Modify the configuration file to separate the name of the urls from the parent directory of the docker-compose</li>
</ul>
<a name="Suggestion"></a>
<h2 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h2>
<p>Can be replaced by </p>
<ul>
<li><a href="http://websockets:9527/" class="external">http://websockets:9527/</a></li>
<li><a href="http://livehandler_1:9528/" class="external">http://livehandler_1:9528/</a></li>
</ul>
<p>See <a href="https://github.com/os-autoinst/openQA/pull/3755" class="external">https://github.com/os-autoinst/openQA/pull/3755</a></p>
openQA Project - action #89755 (Resolved): container: Fix missing shared directories and its perm...https://progress.opensuse.org/issues/897552021-03-09T16:19:23Zilausuchilausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Some directories are missing generating errors like this</p>
<pre><code>gru_1 | Can not create MOJO_TMPDIR : mkdir /var/lib/openqa/share/factory/tmp: Permission denied at /usr/share/openqa/script/../lib/OpenQA/Setup.pm line 306.
</code></pre>
<p>The directories has to be:</p>
<p>/data/factory/iso:rw<br>
/data/factory/hdd:rw<br>
/data/factory/other:rw<br>
/data/factory/tmp:rw<br>
/data/testresults:rw<br>
/data/tests:ro<br>
/data/conf:ro</p>
<p>Also the <code>factory</code> and <code>testresults</code> directories have to be writable by <code>geekotest</code> user in the container</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC 1</strong>: Ensure factory/testresults directories are created</li>
<li><strong>AC 2</strong>: Ensure container user has permissions for these directories</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Does the user in the container have the right permissions?</li>
<li>Does os-autoinst/openQA/... create all folders on demand?</li>
<li>See <a href="https://github.com/os-autoinst/openQA/pull/3755" class="external">https://github.com/os-autoinst/openQA/pull/3755</a></li>
</ul>
openQA Project - action #89749 (New): containers: Allow to the user to choose the source of image...https://progress.opensuse.org/issues/897492021-03-09T15:55:59Zilausuchilausuch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Now only the local build images can be used on the docker-compose. As a user would be nice to give me the option to choose without changing the docker-compose yaml</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<p><strong>AC 1</strong>: The user can choose the images<br>
<strong>AC 2</strong>: Create a test to check that local build images and remote images can be used</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Use docker-compose variables e.g. image: ${OPENQA_WEBUI_IMAGE}</li>
<li>Add the default values to .env file</li>
<li>See <a href="https://github.com/os-autoinst/openQA/pull/3755" class="external">https://github.com/os-autoinst/openQA/pull/3755</a></li>
</ul>
openQA Project - action #88315 (New): Complete the worker container test obtaining the key/secret...https://progress.opensuse.org/issues/883152021-01-28T15:32:32Zilausuchilausuch@suse.com
<a name="Problem"></a>
<h1 >Problem<a href="#Problem" class="wiki-anchor">¶</a></h1>
<p>The ticket <a href="https://progress.opensuse.org/issues/80682" class="external">https://progress.opensuse.org/issues/80682</a> test that the worker container starts and try to connect to the web UI. But this connection cannot be completed because there are not existing credentials by default.</p>
<a name="Acceptance-Criteria"></a>
<h1 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h1>
<ul>
<li>AC1: Create a pair of credentials</li>
<li>AC2: Set the client.conf with the new credentials and check that the worker connects to the web UI without problems.</li>
</ul>
openQA Project - action #88061 (New): Fix premature cancel of a job when strange character is enc...https://progress.opensuse.org/issues/880612021-01-20T13:25:53Zilausuchilausuch@suse.com
<p>Problem<br>
When in tests code is introduced a strange character openQA finished incomplete with this message</p>
<pre><code>Result: incomplete finished about 6 hours ago ( 12:54 minutes )
Reason: backend died: No map for 'Ã' at /usr/lib/os-autoinst/consoles/VNC.pm line 741.
</code></pre>
<p>Example:<br>
<a href="http://10.161.229.197/tests/173" class="external">http://10.161.229.197/tests/173</a></p>
<p>To test that use this lines. Note that the problem is in -–network-alias where the second dash (the bad) is different to the first one (the good)</p>
<pre><code>podman run -d -e POSTGRES_PASSWORD=openqa -e POSTGRES_USER=openqa -e POSTGRES_DB=openqa -–network-alias=db --name db postgres
</code></pre>
<p>In a console podman fails with this error:</p>
<pre><code>Error: unknown shorthand flag: 'â' in -–network-alias=db
</code></pre> openQA Project - coordination #81060 (Blocked): [epic] openQA web UI in kuberneteshttps://progress.opensuse.org/issues/810602020-12-15T06:09:11Zilausuchilausuch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Helm charts allows you to automate the deployment of a complex set of items in a kubernetes environment. These elements are not only limited to pods (containers) but also to configurations (configmaps and secrets), and all the resources they need in the correct order and with the proper checks.</p>
<p>Thanks to the work done in <a class="issue tracker-6 status-15 priority-4 priority-default parent" title="coordination: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containe... (Blocked)" href="https://progress.opensuse.org/issues/80142">#80142</a> we saw how to divide the web UI into parts, which were could be converted into HA and which had to remain standalone. In addition to how we should configure the load balancer to integrate each of the different services that make up the complete web UI.</p>
<p>This ticket proposes to create a helm chart capable of generating a complete and functional deployment of the web UI based on the following prerequisites:</p>
<ul>
<li>There is a pre-existing installation of kubernetes</li>
</ul>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> The complete web UI HA is installed with the DB with the default options</li>
<li><strong>AC2:</strong> The web UI is accessible from outside of the cluster</li>
<li><strong>AC3:</strong> The helm chart is configurable with: Typical and basic parameters and, number of replicas for HA, type of persistence for DB, ...</li>
<li><strong>AC4:</strong> Documentation is completed with instructions of use</li>
<li><strong>AC5:</strong> Deployed together with rancher</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Highly recommended based on work already done in <a class="issue tracker-6 status-15 priority-4 priority-default parent" title="coordination: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containe... (Blocked)" href="https://progress.opensuse.org/issues/80142">#80142</a>, e.g. the existing docker-compose setup</li>
<li><del>Proof-of-concept of either openQA webUI <em>or</em> worker within kubernetes, e.g. using k3s or try rancher directly</del> done for both webUI and worker in <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: [timeboxed:20h][spike] openQA proof-of-concept within kubernetes size:M (Resolved)" href="https://progress.opensuse.org/issues/110524">#110524</a></li>
<li>Use local kubernetes deployments to development purposes (this avoid the infra needs). For instance: minikube, k3s,... </li>
<li>Figure out if is necessary to publish the helm chart and where: <a href="https://helm.sh/docs/howto/chart_releaser_action/">https://helm.sh/docs/howto/chart_releaser_action/</a></li>
<li>Combine with rancher</li>
<li>Ensure proper testing of the charts
<ul>
<li>Create kubernetes cluster inside docker inside GitHub Actions: <a href="https://github.com/marketplace/actions/kind-cluster">https://github.com/marketplace/actions/kind-cluster</a></li>
<li>Look at chart-testing tool: <a href="https://github.com/marketplace/actions/helm-chart-testing">https://github.com/marketplace/actions/helm-chart-testing</a></li>
<li>Try to deploy the chart inside CI</li>
</ul></li>
<li>Add definitions for init containers to allow fetching tests/needles from git repository during installation</li>
<li>As an alternative to git, provide a persistent volume claim template for shared volume (ReadMany) -- think about Longhorn</li>
<li>Add definition for rsyncd container to allow usage of cache service in the worker pod to synchronize data between webui and worker pods</li>
<li>Enhance customization options of the current chart, add common options (like annotations, pod security, replicas count, ...) which are provided by the blank helm templates (reuse initial templates created by <code>helm create</code>)</li>
</ul>
openQA Project - action #80466 (Workable): docker: Base the webUI and worker Dockerfiles in Tumbl...https://progress.opensuse.org/issues/804662020-11-26T15:25:46Zilausuchilausuch@suse.com
<a name="User-story"></a>
<h2 >User story<a href="#User-story" class="wiki-anchor">¶</a></h2>
<p>As developers we want that in order to preserve for our dev environment the Dockerfiles should be build based on Tumbleweed, not Leap 15.2</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> webUI dockerfile is based on Tumbleweed</li>
<li><strong>AC2:</strong> worker dockerfile is based on Tumbleweed</li>
</ul>
openQA Project - action #71188 (Workable): job incomplete with auto_review:"backend died: QEMU ex...https://progress.opensuse.org/issues/711882020-09-10T10:28:59Zilausuchilausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><a href="https://openqa.suse.de/tests/4667727">https://openqa.suse.de/tests/4667727</a> incomplete reason "backend died: QEMU exited unexpectedly, see log for details"</p>
<p><a href="https://openqa.suse.de/tests/4667727/file/autoinst-log.txt">https://openqa.suse.de/tests/4667727/file/autoinst-log.txt</a> shows just:</p>
<pre><code>
[2020-09-09T19:53:48.385 CEST] [debug] <<< testapi::wait_serial(quiet=undef, timeout=1000, expect_not_found=0, record_output=undef, buffer_size=undef, regexp=qr/cmy9h-\d+-/, no_regex=0)
�[32m[2020-09-09T19:53:49.454 CEST] [debug] >>> testapi::wait_serial: (?^:cmy9h-\d+-): ok
�[0m[2020-09-09T19:53:49.454 CEST] [debug] tests/console/force_scheduled_tasks.pm:54 called testapi::assert_script_run
[2020-09-09T19:53:49.454 CEST] [debug] <<< testapi::assert_script_run(cmd="for i in \$(systemctl list-units --type=timer --state=active --no-legend | sed -e 's/\\(\\S\\+\\)\\.timer\\s.*/\\1/'); do echo \"Triggering systemd timed service \$i\" && systemctl start \$i && systemctl mask \$i.{service,timer}; done", quiet=undef, fail_message="", timeout=1000)
[2020-09-09T19:53:49.454 CEST] [debug] tests/console/force_scheduled_tasks.pm:54 called testapi::assert_script_run
[2020-09-09T19:53:49.454 CEST] [debug] <<< testapi::type_string(string="for i in \$(systemctl list-units --type=timer --state=active --no-legend | sed -e 's/\\(\\S\\+\\)\\.timer\\s.*/\\1/'); do echo \"Triggering systemd timed service \$i\" && systemctl start \$i && systemctl mask \$i.{service,timer}; done", max_interval=250, wait_screen_changes=0, wait_still_screen=0, timeout=30, similarity_level=47)
�[33m[2020-09-09T19:53:52.124 CEST] [info] ::: OpenQA::Qemu::Proc::save_state: Saving QEMU state to qemu_state.json
�[0m�[37m[2020-09-09T19:53:52.127 CEST] [debug] sending magic and exit
�[0m�[37m[2020-09-09T19:53:52.127 CEST] [debug] received magic close
�[0m�[37m[2020-09-09T19:53:52.128 CEST] [debug] THERE IS NOTHING TO READ 16 5 4
�[0m�[37m[2020-09-09T19:53:52.128 CEST] [debug] stopping command server 28437 because test execution ended
�[0m�[37m[2020-09-09T19:53:52.128 CEST] [debug] isotovideo: informing websocket clients before stopping command server: http://127.0.0.1:20053/Bx3fOTDMBl3VvYnl/broadcast
�[0m�[37m[2020-09-09T19:53:52.142 CEST] [debug] commands process exited: 0
�[0m�[37m[2020-09-09T19:53:52.151 CEST] [debug] backend process exited: 0
�[0m�[37m[2020-09-09T19:53:52.177 CEST] [debug] Driver backend collected unknown process with pid 28559 and exit status: 0
�[0m�[37m[2020-09-09T19:53:52.177 CEST] [debug] done with command server
�[0m�[37m[2020-09-09T19:53:52.177 CEST] [debug] stopping autotest process 28441
�[0m�[37m[2020-09-09T19:53:52.177 CEST] [debug] autotest received signal TERM, saving results of current test before exiting
�[0m�[37m[2020-09-09T19:53:52.187 CEST] [debug] [autotest] process exited: 1
�[0m�[37m[2020-09-09T19:53:53.288 CEST] [debug] done with autotest process
�[0m�[37m[2020-09-09T19:53:53.288 CEST] [debug] isotovideo failed
�[0m�[37m[2020-09-09T19:53:53.288 CEST] [debug] stopping backend process 28500
�[0m�[37m[2020-09-09T19:53:53.288 CEST] [debug] done with backend process
�[0m28430: EXIT 1
[2020-09-09T19:53:53.0361 CEST] [info] [pid:1576] Isotovideo exit status: 1
[2020-09-09T19:53:53.0387 CEST] [info] [pid:1576] +++ worker notes +++
[2020-09-09T19:53:53.0387 CEST] [info] [pid:1576] End time: 2020-09-09 17:53:53
[2020-09-09T19:53:53.0387 CEST] [info] [pid:1576] Result: died
[2020-09-09T19:53:53.0393 CEST] [info] [pid:37797] Uploading logs_from_installation_system-y2logs.tar.bz2
[2020-09-09T19:54:22.0706 CEST] [info] [pid:37797] Uploading video.ogv
[2020-09-09T19:59:29.0220 CEST] [info] [pid:37797] Uploading vars.json
[2020-09-09T19:59:29.0786 CEST] [info] [pid:37797] Uploading autoinst-log.txt
</code></pre>
<a name="Steps-to-reproduce"></a>
<h2 >Steps to reproduce<a href="#Steps-to-reproduce" class="wiki-anchor">¶</a></h2>
<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">https://raw.githubusercontent.com/os-autoinst/scripts/master/openqa-query-for-job-label</a> ,<br>
for example to look for this ticket call <code>openqa-query-for-job-label poo#71188</code></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> A user better understands what could have gone wrong and the next step is clear what to do</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Regardless of what happened maybe just restarting would have helped</li>
<li>Check if there is any information on the worker host for this time</li>
</ul>
openQA Project - action #65954 (Rejected): Create a way to check which jobs contain a testhttps://progress.opensuse.org/issues/659542020-04-22T06:03:01Zilausuchilausuch@suse.com
<p>Using this url <a href="https://openqa.suse.de/admin/test_suites" class="external">https://openqa.suse.de/admin/test_suites</a> we could find a test. <br>
And therefore in "All tests" page <a href="https://openqa.suse.de/tests" class="external">https://openqa.suse.de/tests</a> page we could try to find this test in last finished jobs list. <br>
But sometimes it doesn't appears because this list is limited to 500 jobs.<br>
I could be interesting to get which jobs contain this test</p>