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>
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>
QA - action #95854 (Rejected): Grafana doesn't show information during some minutes, but also we ...https://progress.opensuse.org/issues/958542021-07-22T10:17:59Zilausuchilausuch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>On 2021-07-22 10:14 we can grafana is not showing getting any results of the Webui summary ping<br>
<a href="https://stats.openqa-monitor.qa.suse.de/d/WebuiDb/webui-summary?tab=alert&viewPanel=76&orgId=1&from=1626941518339&to=1626942588243" class="external">https://stats.openqa-monitor.qa.suse.de/d/WebuiDb/webui-summary?tab=alert&viewPanel=76&orgId=1&from=1626941518339&to=1626942588243</a><br>
And we can check that we have increase of CPU after the recovery<br>
<a href="https://stats.openqa-monitor.qa.suse.de/d/WebuiDb/webui-summary?tab=alert&viewPanel=25&orgId=1" class="external">https://stats.openqa-monitor.qa.suse.de/d/WebuiDb/webui-summary?tab=alert&viewPanel=25&orgId=1</a><br>
<a href="https://stats.openqa-monitor.qa.suse.de/d/WebuiDb/webui-summary?tab=alert&viewPanel=25&orgId=1&from=1628060971570&to=1628663436435" class="external">https://stats.openqa-monitor.qa.suse.de/d/WebuiDb/webui-summary?tab=alert&viewPanel=25&orgId=1&from=1628060971570&to=1628663436435</a></p>
<p>During the daily we checked that there weren't a huge quantity of pending jobs to explain the amount of CPU on the recovery.</p>
openQA Project - action #95768 (New): containers: the single_container_test shows this error "Per...https://progress.opensuse.org/issues/957682021-07-21T09:02:09Zilausuchilausuch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Thanks to a previous issue <a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" title="action: [sporadic] containers: eventually the tests fails on single_container_webui step with the error "... (Resolved)" href="https://progress.opensuse.org/issues/95179">#95179</a> we could see in the logs that the webui has permissions problems on the "factory" directory<br>
e.g. <a href="https://openqa.opensuse.org/tests/1830297#step/single_container_webui/107" class="external">https://openqa.opensuse.org/tests/1830297#step/single_container_webui/107</a></p>
<p>The reason is because the directory has the root user (in the container) but the webui is executed with the geekotest user. </p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC 1</strong>: webui can create the needed directories in /var/lib/openqa/share/factory</li>
</ul>
<a name="Suggestion"></a>
<h2 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h2>
<ul>
<li>Currently if the container doesn't fail the logs are not be printed, so print "docker logs openqa_webui" the logs before destroy the container</li>
<li>Check if there are other directories that require to be created from the webui and can be created</li>
</ul>
openQA Project - action #93177 (New): containers: webui doesn't has the credentials to connect to...https://progress.opensuse.org/issues/931772021-05-27T11:42:47Zilausuchilausuch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>The PR <a href="https://github.com/os-autoinst/openQA/pull/3915" class="external">https://github.com/os-autoinst/openQA/pull/3915</a> introduces a test of launching a job, but in the webui logs we can appreciate this error<br>
I separated this ticket from <a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" title="action: containers: Web UI cannot connect to scheduler (Resolved)" href="https://progress.opensuse.org/issues/92833">#92833</a> because It requires go deeper in testing and also see if there are other alternatives to the provided solution (below)</p>
<pre><code class="text syntaxhl" data-language="text">webui_2 | {"error":"Not authorized"}
</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> The communication from the webui with the scheduler is authorized</li>
</ul>
<a name="Ideas-and-previous-tests"></a>
<h2 >Ideas and previous tests<a href="#Ideas-and-previous-tests" class="wiki-anchor">¶</a></h2>
<p>Adding this to client.conf works.</p>
<pre><code class="text syntaxhl" data-language="text">[scheduler]\nkey = 1234567890ABCDEF\nsecret = 1234567890ABCDEF\n
</code></pre> openQA Project - action #91752 (Resolved): jenkins: Multiple missing fields and errors in configu...https://progress.opensuse.org/issues/917522021-04-26T11:10:31Zilausuchilausuch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Saving a new configuration is necessary to accomplish <a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" title="action: openQA-in-openQA tests always fail and results do not impact submission pipeline (Resolved)" href="https://progress.opensuse.org/issues/88754">#88754</a>. But it's impossible because multiple missing fields and errors in the UI configuration.<br>
It is not possible to save new changes.</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC 1</strong>: The configuration can be changed and saved</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Configuration url: <a href="http://jenkins.qa.suse.de/view/openQA-in-openQA/job/monitor-openQA_in_openQA-TW/configure" class="external">http://jenkins.qa.suse.de/view/openQA-in-openQA/job/monitor-openQA_in_openQA-TW/configure</a></li>
</ul>
openQA Project - action #90995 (New): containers: Reduce the testing time for "webui-docker-compose"https://progress.opensuse.org/issues/909952021-04-12T10:11:36Zilausuchilausuch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>More than 30 minutes to run this test is excessive.</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC 1</strong>: Research where the test consumes the time</li>
<li><strong>AC 2</strong>: Reduce the testing time</li>
</ul>
<a name="Reference"></a>
<h2 >Reference<a href="#Reference" class="wiki-anchor">¶</a></h2>
<ul>
<li><a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: containers: Fix github test "webui-docker-compose" timeout (Resolved)" href="https://progress.opensuse.org/issues/90767">#90767</a></li>
</ul>
openQA Project - action #89731 (Resolved): containers: The deploy using docker-compose is not sta...https://progress.opensuse.org/issues/897312021-03-09T11:50:40Zilausuchilausuch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>The command 'docker-compose up' is executed without errors in normal circustancies, but sometimes some of the containers fail later after the docker-compose has finished.</p>
<pre><code>$ docker-compose up -d
Creating webui_db_1 ... done
Creating webui_nginx_1 ... done
Creating webui_data_1 ... done
Creating webui_scheduler_1 ... done
Creating webui_webui_1 ... done
Creating webui_webui_2 ... done
Creating webui_gru_1 ... done
Creating webui_websockets_1 ... done
Creating webui_livehandler_1 ... done
$ echo $?
0
</code></pre><pre><code>docker-compose ps
Name Command State Ports
----------------------------------------------------------------------------------------------------------------------------------------
webui_data_1 /bin/sh -c /usr/bin/tail - ... Up
webui_db_1 docker-entrypoint.sh postgres Up 5432/tcp
webui_gru_1 /root/run_openqa.sh Up 443/tcp, 80/tcp, 9526/tcp, 9527/tcp, 9528/tcp, 9529/tcp
webui_livehandler_1 /root/run_openqa.sh Up 443/tcp, 80/tcp, 9526/tcp, 9527/tcp, 0.0.0.0:9528->9528/tcp, 9529/tcp
webui_nginx_1 /entrypoint.sh Up 0.0.0.0:9526->9526/tcp
webui_scheduler_1 /root/run_openqa.sh Exit 255
webui_websockets_1 /root/run_openqa.sh Up 443/tcp, 80/tcp, 9526/tcp, 0.0.0.0:9527->9527/tcp, 9528/tcp, 9529/tcp
webui_webui_1 /root/run_openqa.sh Up 443/tcp, 80/tcp, 0.0.0.0:32789->9526/tcp, 9527/tcp, 9528/tcp, 9529/tcp
webui_webui_2 /root/run_openqa.sh Up 443/tcp, 80/tcp, 0.0.0.0:32790->9526/tcp, 9527/tcp, 9528/tcp, 9529/tcp
</code></pre>
<p>The errors in schedulers are:</p>
<pre><code>scheduler_1 | failed to run SQL in /usr/share/openqa/script/../dbicdh/PostgreSQL/deploy/90/001-auto-__VERSION.sql: DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator::try {...} (): DBI Exception: DBD::Pg::db do failed: ERROR: duplicate key value violates unique constraint "pg_type_typname_nsp_index"
scheduler_1 | DETAIL: Key (typname, typnamespace)=(dbix_class_deploymenthandler_versions_id_seq, 2200) already exists. at inline delegation in DBIx::Class::DeploymentHandler for deploy_method->deploy (attribute declared in /usr/lib/perl5/vendor_perl/5.26.1/DBIx/Class/DeploymentHandler/WithApplicatorDumple.pm at line 51) line 18
scheduler_1 | (running line 'CREATE TABLE dbix_class_deploymenthandler_versions ( id serial NOT NULL, version character varying(50) NOT NULL, ddl text, upgrade_sql text, PRIMARY KEY (id), CONSTRAINT dbix_class_deploymenthandler_versions_version UNIQUE (version) )') at /usr/lib/perl5/vendor_perl/5.26.1/DBIx/Class/DeploymentHandler/DeployMethod/SQL/Translator.pm line 263.
scheduler_1 | DBIx::Class::Storage::TxnScopeGuard::DESTROY(): A DBIx::Class::Storage::TxnScopeGuard went out of scope without explicit commit or error. Rolling back. at /usr/share/openqa/script/openqa-scheduler line 0
scheduler_1 | DBIx::Class::Storage::TxnScopeGuard::DESTROY(): A DBIx::Class::Storage::TxnScopeGuard went out of scope without explicit commit or error. Rolling back. at /usr/share/openqa/script/openqa-scheduler line 0
</code></pre>
<p>The problem is that every container that uses openqa_webui image (webui_webui, webui_websockets, webui_scheduler, webui_livehandler) try to initialize the DB tables. And as all the containers are initialized at the same time surges conflicts.</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC 1</strong>: All the containers remain up after execute docker-compose up
<del>* <strong>AC 2</strong>: Expand the docker-compose CI test to include this case</del></li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Use dependencies (depends_on) based on health-checks to sort the startup of all the containers.</li>
<li>Check current solution on <a href="https://github.com/os-autoinst/openQA/pull/3755">https://github.com/os-autoinst/openQA/pull/3755</a></li>
</ul>
openQA Project - action #88482 (Resolved): Two absolute paths concatenated to form a default need...https://progress.opensuse.org/issues/884822021-02-08T13:07:40Zilausuchilausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Sometimes a job execution fails with this error</p>
<pre><code>needles_dir not found: /var/lib/openqa/share/tests/opensuse/var/lib/openqa/share/tests/opensuse/products/opensuse/needles (check vars.json?) at /usr/lib/os-autoinst/needle.pm line 330.
</code></pre>
<p>Is concatenating two absolute paths (<a href="https://github.com/os-autoinst/os-autoinst/blob/adbb28bc61ce4f21a55d07399eac7d48badc6b6f/needle.pm#L328" class="external">https://github.com/os-autoinst/os-autoinst/blob/adbb28bc61ce4f21a55d07399eac7d48badc6b6f/needle.pm#L328</a>) when needles directory doesn't exist.</p>
<a name="Reproduction"></a>
<h2 >Reproduction<a href="#Reproduction" class="wiki-anchor">¶</a></h2>
<p>Remove the directory needles from /var/lib/openqa/share/tests/opensuse/products/opensuse</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>AC1: Needles folder has a working default or aborts if PRODUCT_DIR/needles doesn't exist</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Look into logic in <code>needle.pm</code></li>
<li>Improve error message to reveal relevant variables instead of hinting at <code>vars.json</code> i.e. <code>NEEDLES_DIR</code>, <code>CASEDIR</code> and <code>default_needles_dir</code></li>
<li>Log the missing <code>PRODUCTDIR}/needles</code> if this affects the default nedles folder to be used here</li>
</ul>
<a name="Work-around"></a>
<h2 >Work-around<a href="#Work-around" class="wiki-anchor">¶</a></h2>
<ul>
<li>Create a folder <code>PRODUCTDIR}/needles</code></li>
</ul>
openQA Project - action #88187 (Resolved): Set the addresses in the "internal clients" configurablehttps://progress.opensuse.org/issues/881872021-01-25T10:46:37Zilausuchilausuch@suse.com
<p>Problem:<br>
The listening addresses are hardcoded to localhost within the different "internal clients" (e.g. lib/OpenQA/Scheduler/Client.pm and lib/OpenQA/WebSockets/Client.pm).<br>
This limitation prevents running the different parts of the web UI on different hosts, e.g. a load balanced environment because the different components (scheduler, websockets, …) cannot communicate witch each other.</p>
<p>Suggested solution:<br>
Read an environment variable like OPENQA_SCHEDULER_HOST. This environment variable needs then be supplied to all other containers. <br>
Note: It looks like the livehandler and gru don't have a client. That likely means it is no necessary to care about them as no other services access them (via HTTP).</p>
<p>AC1: The addresses in the "internal clients" are configurable</p>
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 - 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>