openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-02-08T09:25:36ZopenSUSE Project Management Tool
Redmine openQA Project - action #155173 (Resolved): [openqa-in-openqa] [sporadic] test fails in openqa_wo...https://progress.opensuse.org/issues/1551732024-02-08T09:25:36Ztinitatina.mueller+trick-redmine@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install_nginx@64bit-2G fails in<br>
<a href="https://openqa.opensuse.org/tests/3922710/modules/openqa_worker/steps/9" class="external">openqa_worker</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.opensuse.org/tests/3922710" class="external">:TW.26398</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.opensuse.org/tests/3922125" class="external">:TW.26397</a> (or more recent)</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Lookup older tickets and add as reference about adding os-autoinst-setup-multi-machine to openQA-in-openQA tests</li>
<li>Try to reproduce and fix or simply apply a mitigation as applicable, e.g. increase timeout or retry or something</li>
<li>The proper place to fix might be in the test code but could also be in os-autoinst-setup-multi-machine itself or even further low-level</li>
</ul>
<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.opensuse.org/tests/latest?arch=x86_64&distri=openqa&flavor=dev&machine=64bit-2G&test=openqa_install_nginx&version=Tumbleweed" class="external">latest</a></p>
openQA Project - action #155170 (Resolved): [openqa-in-openqa] [sporadic] test fails in test_runn...https://progress.opensuse.org/issues/1551702024-02-08T09:24:12Ztinitatina.mueller+trick-redmine@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install_multimachine@64bit-4G fails in<br>
<a href="https://openqa.opensuse.org/tests/3923320/modules/test_running/steps/5" class="external">test_running</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.opensuse.org/tests/3923320" class="external">:TW.26399</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.opensuse.org/tests/3922709" class="external">:TW.26398</a> (or more recent)</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Take a look into <a href="https://openqa.opensuse.org/tests/3923320/file/test_running-mm_testresults.txz" class="external">https://openqa.opensuse.org/tests/3923320/file/test_running-mm_testresults.txz</a></li>
<li>Apply same steps as in <a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" title="action: [openqa-in-openqa] [sporadic] test fails in openqa_worker: os-autoinst-setup-multi-machine timed ... (Resolved)" href="https://progress.opensuse.org/issues/155173">#155173</a> but at a slightly different code location</li>
<li>Consider if this issue is actually the same as <a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" title="action: [openqa-in-openqa] [sporadic] test fails in openqa_worker: os-autoinst-setup-multi-machine timed ... (Resolved)" href="https://progress.opensuse.org/issues/155173">#155173</a></li>
<li><em>DONE</em> Investigate if the error message from dmesg <code>Failed to associated timeout policy</code>ovs_test_tp'` could be related to the failure no, also happens in passed runs</li>
</ul>
<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.opensuse.org/tests/latest?arch=x86_64&distri=openqa&flavor=dev&machine=64bit-4G&test=openqa_install_multimachine&version=Tumbleweed" class="external">latest</a></p>
openQA Infrastructure - action #153328 (Resolved): jenkins fails in submit-openQA-TW-to-oS_Fctry,...https://progress.opensuse.org/issues/1533282024-01-10T09:32:23Znicksingernsinger@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><a href="http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/975" class="external">http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/975</a> fails with:</p>
<pre><code>+ curl -sS 'https://api.opensuse.org/public/build/devel:openQA:tested/_result?repository=openSUSE_Factory&package=os-autoinst'
+ grep -e '\(unknown\|blocked\|scheduled\|dispatching\|building\|signing\|finished\)'
curl: (28) Failed to connect to api.opensuse.org port 443 after 129973 ms: Couldn't connect to server
…
+ osc service wait devel:openQA os-autoinst-distri-opensuse-deps
Server returned an error: HTTP Error 400: Bad Request
The service for project 'devel:openQA' package 'os-autoinst-distri-opensuse-deps' failed
service error: '
+ rm -rf /tmp/os-autoinst-obs-auto-submit-vn8K
</code></pre>
<p>The error message unfortunately doesn't tell us much. Maybe this can be improved for the future? Error 400 indicates we're using the API wrong, did something change we didn't notice?</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Check the jenkins job if error output can be fixed</li>
<li>Check if something with OBS changed and we need to update the client or might have to adapt our script(s)</li>
<li>Run the failing command manually, find out if it's reproducible/sporadic?
<ul>
<li>It works locally on TW and Leap 15.5</li>
</ul></li>
<li>jenkins.qe.nue2.suse.org has the same osc package version as other hosts so it's not an outdated package</li>
<li>Ask for help in OBS related channels</li>
<li>Improve the error handling in the pipleine script</li>
</ul>
openQA Project - action #138203 (Resolved): [openQA-in-openQA] CI jobs show error but don't fail ...https://progress.opensuse.org/issues/1382032023-10-18T13:00:44Zokurzokurz@suse.com
<p><a href="https://progress.opensuse.org/issues/138203" class="external">https://progress.opensuse.org/issues/138203</a></p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><a href="https://github.com/os-autoinst/os-autoinst-distri-openQA/actions/runs/6560371820/job/17817854926?pr=147#step:5:11" class="external">https://github.com/os-autoinst/os-autoinst-distri-openQA/actions/runs/6560371820/job/17817854926?pr=147#step:5:11</a> says</p>
<pre><code>{"count":4,"failed":[{"error_message":"The PUBLISH_HDD_1 cannot include \/ in value at \/usr\/share\/openqa\/script\/..\/lib\/OpenQA\/Schema\/ResultSet\/Jobs.pm line 122.\n","job_name":"openqa_install+publish"}],"ids":[3655002,3655003,3655004,3655005],"scheduled_product_id":339600}
</code></pre>
<p>maybe that's the reason why openqa_install+publish does not show up?</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> error messages returned from the openQA API cause the CI pipeline to abort</li>
<li><strong>AC2:</strong> A default openQA installation using apache is running as part of every pull request to os-autoinst-distri-openQA</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Maybe we don't want to call "openqa_install+publish" directly in pull requests as that would take rather long to publish a qcow image and also it might overwrite the production one based on how PUBLISH_HDD_1 is configured. But on the other hand having a qcow file published that one can use directly for investigation and development would be nice. We should check how long it takes with/without publishing and decide what is the good approach for pull request triggered tests and ensure that we do have a default openQA installation using apache is running as part of every pull request to os-autoinst-distri-openQA</li>
<li>Ensure that in the CI job errors abort the CI with according error as well so that such errors don't go unnoticed (change openqa-cli exit code in case of errors)</li>
</ul>
openQA Project - action #133349 (Resolved): openQA-in-openQA tests fail in zypper command with 'M...https://progress.opensuse.org/issues/1333492023-07-26T08:03:02Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><a href="https://openqa.opensuse.org/tests/3455846#step/openqa_webui/13" class="external">https://openqa.opensuse.org/tests/3455846#step/openqa_webui/13</a> shows a problem in zypper</p>
<pre><code>Error code: Curl error 47
Error message: Maximum (6) redirects followed
</code></pre>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> No more failed redirects</li>
<li><strong>AC2:</strong> All network-related retry calls use exponential backoff</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<p>We already use retry as visible in<br>
<a href="https://openqa.opensuse.org/tests/3455846/video?filename=video.webm&t=5.5,6" class="external">https://openqa.opensuse.org/tests/3455846/video?filename=video.webm&t=5.5,6</a><br>
but we don't use exponential backoff. Maybe just add that?</p>
<a name="Workaround"></a>
<h2 >Workaround<a href="#Workaround" class="wiki-anchor">¶</a></h2>
<p>Retrigger the job</p>
openQA Project - action #132335 (Resolved): In openqa-in-openqa use scenario definitions instead ...https://progress.opensuse.org/issues/1323352023-07-05T11:05:08Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>We have both <a href="https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/scenario-definitions.yaml" class="external">https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/scenario-definitions.yaml</a> as well as <a href="https://github.com/os-autoinst/opensuse-jobgroups/blob/master/job_groups/openqa.yaml" class="external">https://github.com/os-autoinst/opensuse-jobgroups/blob/master/job_groups/openqa.yaml</a><br>
and we should not duplicate. Let's ensure that the scenario definitions file can take over completely including the test suite descriptions and then delete the job group templates.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> <a href="https://github.com/os-autoinst/opensuse-jobgroups/blob/master/job_groups/openqa.yaml" class="external">https://github.com/os-autoinst/opensuse-jobgroups/blob/master/job_groups/openqa.yaml</a> does not duplicate anything anymore from <a href="https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/scenario-definitions.yaml" class="external">https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/scenario-definitions.yaml</a></li>
<li><strong>AC2:</strong> We still have separate, differing test definitions for pull requests and for what is triggered nightly</li>
<li><strong>AC3:</strong> It is clear from tests where the schedule is defined and where it needs to be changed</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Try to put in the scenario definitions URL into the isos post call in the according calls used in <a href="http://jenkins.qa.suse.de/" class="external">http://jenkins.qa.suse.de/</a> jobs so that we at best we don't need the job templates in the job group anymore</li>
<li>Include the test suite descriptions from job templates into scenario definitions</li>
<li>Consider the actual differences where they make sense, e.g. in job templates we have a "publish" job publishing an appliance which we don't want to trigger in every pull request CI test run. Maybe just handle the publish test completely separate with an explicit scenario definition file that is triggered or something. Maybe separate flavors like "dev" and our "publish" variant within the same file so that we don't need to duplicate machine, etc., in multiple files</li>
<li>If all works well empty/delete <a href="https://github.com/os-autoinst/opensuse-jobgroups/blob/master/job_groups/openqa.yaml" class="external">https://github.com/os-autoinst/opensuse-jobgroups/blob/master/job_groups/openqa.yaml</a></li>
</ul>
openQA Project - action #131450 (Workable): [openQA-in-openQA] test fails in openqa_webui due to ...https://progress.opensuse.org/issues/1314502023-06-27T08:23:42Ztinitatina.mueller+trick-redmine@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_from_containers@64bit-2G fails in<br>
<a href="https://openqa.opensuse.org/tests/3383995/modules/openqa_webui/steps/7" class="external">openqa_webui</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: <a href="mailto:okurz@suse.de">okurz@suse.de</a> Test for running openQA itself from containers. To be used with "openqa" distri. Introduced retry on the job level due to <a href="https://progress.opensuse.org/issues/108665" class="external">https://progress.opensuse.org/issues/108665</a> as there can still be sporadic network issues sometimes.</p>
<p>The test tries to execute</p>
<pre><code>sudo -u bernhard gsettiupdates false
</code></pre>
<p>instead of</p>
<pre><code>sudo -u bernhard gsettings set org.gnome.software download-updates false
</code></pre>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.opensuse.org/tests/3383995" class="external">:TW.21237</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.opensuse.org/tests/3383819" class="external">:TW.21236</a> (or more recent)</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>The scenario is sufficently stable, i.e. at least 100 stable jobs in a row (3/100 -> probability is below 5% that there is a failed job every 30 jobs)</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Try to investigate the failed job if it's still there. Maybe something made the system very busy</li>
<li>Try to reproduce it following <a href="https://progress.opensuse.org/projects/openqatests/wiki/Wiki#Statistical-investigation" class="external">https://progress.opensuse.org/projects/openqatests/wiki/Wiki#Statistical-investigation</a> or use "openqa-clone-set" . If not reproducible then reject</li>
<li>If it can be reproduced then gather more information from the SUT, e.g. load, free memory, system journal, etc.</li>
</ul>
<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.opensuse.org/tests/latest?arch=x86_64&distri=openqa&flavor=dev&machine=64bit-2G&test=openqa_from_containers&version=Tumbleweed" class="external">latest</a></p>
openQA Project - action #130369 (Resolved): [spike][timeboxed:20h] Reduce duplication of openQA-i...https://progress.opensuse.org/issues/1303692023-06-05T08:28:25Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p><a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/tests/openqa" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/tests/openqa</a> started mostly as a "copy&paste" variant of <a href="https://github.com/os-autoinst/os-autoinst-distri-openQA/" class="external">https://github.com/os-autoinst/os-autoinst-distri-openQA/</a> as commented in<br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6595#pullrequestreview-194607032" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6595#pullrequestreview-194607032</a> . Recent incidents like <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: openqa_bootstrap: fetchneedles not called during openqa-bootstrap size:S (Resolved)" href="https://progress.opensuse.org/issues/130201">#130201</a> show that we suffer from "I thought we fixed this bug already!"-problems recurringly, … who would have thought that? Let's try to evaluate what options we have regarding enfostering reuse of code, maybe use wheels here as well?</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Keep <a class="issue tracker-4 status-12 priority-4 priority-default child" title="action: os-autoinst/wheel-boot which can be used to test os-autoinst/wheel-launcher size:M (Workable)" href="https://progress.opensuse.org/issues/115019">#115019</a> and <a class="issue tracker-4 status-1 priority-4 priority-default child" title="action: os-autoinst-plugin as a wheel helper tool (New)" href="https://progress.opensuse.org/issues/115013">#115013</a> in mind and play around with the code to see how we can reuse some or at best all code</li>
<li>Optional: Find out why <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: openqa_bootstrap: fetchneedles not called during openqa-bootstrap size:S (Resolved)" href="https://progress.opensuse.org/issues/130201">#130201</a> was hit in openSUSE Tumbleweed and not already in <a href="https://openqa.opensuse.org/group_overview/24" class="external">https://openqa.opensuse.org/group_overview/24</a> and if possible fix that from happening again in the future</li>
</ul>
openQA Project - action #129724 (Resolved): [tools] test fails in test_distribution, can not reac...https://progress.opensuse.org/issues/1297242023-05-23T08:43:36Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install+publish@64bit-2G fails in<br>
<a href="https://openqa.opensuse.org/tests/3310592/modules/test_distribution/steps/7" class="external">test_distribution</a></p>
<p><a href="https://openqa.opensuse.org/tests/3310592#comment-421808" class="external">https://openqa.opensuse.org/tests/3310592#comment-421808</a> shows that the issue reproduces and is likely no product nor test regression so infrastructure.</p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: <a href="mailto:okurz@suse.de">okurz@suse.de</a> Test for installation of openQA itself. To be used with "openqa" distri. Publishes an qcow2 image including the openQA installation ready to run as an appliance.</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.opensuse.org/tests/3310592" class="external">:TW.20660</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.opensuse.org/tests/3310546" class="external">:TW.20659</a> (or more recent)</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li> Is it a temporary problem with download.opensuse.org? If already fixed in the meantime then just retry, monitor, resolve</li>
<li>Do we need more retries to cover that problem?</li>
<li>Consider investigation calls in a post_fail_hook to check network or something</li>
</ul>
<a name="Rollback-steps"></a>
<h2 >Rollback steps<a href="#Rollback-steps" class="wiki-anchor">¶</a></h2>
<ul>
<li>Enable <a href="http://jenkins.qa.suse.de/job/trigger-openQA_in_openQA-TW/" class="external">http://jenkins.qa.suse.de/job/trigger-openQA_in_openQA-TW/</a> again and remove note from job description</li>
</ul>
<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.opensuse.org/tests/latest?arch=x86_64&distri=openqa&flavor=dev&machine=64bit-2G&test=openqa_install%2Bpublish&version=Tumbleweed" class="external">latest</a></p>
openQA Project - action #126680 (Resolved): [openQA-in-openQA] no candidate needle with tag(s) 'b...https://progress.opensuse.org/issues/1266802023-03-27T11:06:05Zlivdywanliv.dywan@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Apparently the <a href="https://openqa.opensuse.org/tests/3193538#step/worker/3" class="external">worker</a> tests in openQA-in-openQA are broken:</p>
<pre><code># Test died: no candidate needle with tag(s) 'boot-menu, openqa-desktop' matched
</code></pre>
<p><a href="https://openqa.opensuse.org/tests/3193538#step/worker/3" class="external">https://openqa.opensuse.org/tests/3193538#step/worker/3</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong>: openQA-in-openQA worker module passes consistently</li>
<li><strong>AC2</strong>: The test is less dependent on GNOME design changes</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Look into providing the missing needle</li>
<li>Adapt the test case accordingly</li>
<li>Don't use a GNOME desktop which frequently undergoes design changes e.g. gmrun, icewm, openbox</li>
</ul>
openQA Project - action #124143 (Resolved): openqa-in-openqa test fails because text color change...https://progress.opensuse.org/issues/1241432023-02-08T14:26:34Znicksingernsinger@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>To my understanding the color of our header-text got slightly more grey (see <a href="https://openqa.opensuse.org/tests/3105702#step/dashboard/9" class="external">https://openqa.opensuse.org/tests/3105702#step/dashboard/9</a>) which reduces readability.<br>
Either the test needle needs to be adjusted or the default in Firefox chanced and we need to define an explicit text color now.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong>: Tests are not failing because of needle matches</li>
<li><strong>AC2</strong>: It is ensured contrast is generally sensible</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Find out what's causing uninteded color changes</li>
<li>If necessery add an explicit override</li>
<li>See what unintended side-effects came from <a href="https://github.com/os-autoinst/openQA/pull/4993#issuecomment-1422681898" class="external">https://github.com/os-autoinst/openQA/pull/4993#issuecomment-1422681898</a></li>
</ul>
<a name="Out-of-scope"></a>
<h2 >Out of scope<a href="#Out-of-scope" class="wiki-anchor">¶</a></h2>
<ul>
<li>Implement a theme that has specific contrast requirements</li>
</ul>
openQA Project - action #123873 (Resolved): openQA test using wheel repo fails to clone: auto_rev...https://progress.opensuse.org/issues/1238732023-02-01T18:12:54Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><a href="https://openqa.opensuse.org/tests/3088469" class="external">https://openqa.opensuse.org/tests/3088469</a> incompleted with</p>
<pre><code>[2023-02-01T16:53:44.341388+01:00] [debug] [pid:45919] git hash in openqa: dc8b61dc63c391f46b33d788a775a2d2acf87a1c
[2023-02-01T16:53:44.345518+01:00] [info] [pid:45919] ::: OpenQA::Isotovideo::Utils::clone_git: Cloning git URL 'https://github.com/os-autoinst/os-autoinst-wheel-launcher.git'
[2023-02-01T16:53:54.371593+01:00] [debug] [pid:45919] Cloning into 'os-autoinst-wheel-launcher'...
fatal: unable to access 'https://github.com/os-autoinst/os-autoinst-wheel-launcher.git/': Could not resolve host: github.com
Unable to clone Git repository 'https://github.com/os-autoinst/os-autoinst-wheel-launcher.git' specified via openqa/wheels.yaml (see log for details) at /usr/lib/os-autoinst/OpenQA/Isotovideo/Utils.pm line 52.
45919: EXIT 1
</code></pre>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>certainly github.com was not unresolvable for long so the error shouldn't cause fatal aborts</p>
openQA Tests - action #122830 (Resolved): [tools][openQA-in-openQA][sporadic] test fails in login...https://progress.opensuse.org/issues/1228302023-01-09T10:57:40Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install+publish@64bit-2G fails in<br>
<a href="https://openqa.opensuse.org/tests/3022232/modules/login/steps/1" class="external">login</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.opensuse.org/tests/3022232" class="external">:TW.14539</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.opensuse.org/tests/3022225" class="external">:TW.14538</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.opensuse.org/tests/latest?arch=x86_64&distri=openqa&flavor=dev&machine=64bit-2G&test=openqa_install%2Bpublish&version=Tumbleweed" class="external">latest</a></p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Confirm why the needle match doesn't get the area anyway. Maybe openQA ends up clicking on the popup</li>
<li>See if we don't have existing code handling similar popups, or try to disable the survey (app.normandy.enabled = false)</li>
<li>From the video it looks to be racy. The login matches just before the popup comes up
<ul>
<li><a href="https://www.askvg.com/tip-disable-surveys-rate-your-experience-out-of-date-notifications-in-firefox/" class="external">https://www.askvg.com/tip-disable-surveys-rate-your-experience-out-of-date-notifications-in-firefox/</a></li>
</ul></li>
</ul>
openQA Project - action #122440 (Resolved): [sporadic] openQA Assetpack download can fail on init...https://progress.opensuse.org/issues/1224402022-12-25T11:25:10Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><a href="https://openqa.opensuse.org/tests/2978761/logfile?filename=openqa_webui-openqa_nohup_out.txt" class="external">https://openqa.opensuse.org/tests/2978761/logfile?filename=openqa_webui-openqa_nohup_out.txt</a> shows</p>
<pre><code>[info] Caching "https://cdn.datatables.net/1.10.16/css/dataTables.bootstrap4.css" to "/root/openQA/script/../assets/cache/cdn.datatables.net/1.10.16/css/dataTables.bootstrap4.css".
[info] Caching "https://cdn.jsdelivr.net/npm/fork-awesome@1.2.0/css/fork-awesome.min.css" to "/root/openQA/script/../assets/cache/cdn.jsdelivr.net/npm/fork-awesome@1.2.0/css/fork-awesome.min.css".
[warn] [AssetPack] Unable to download https://raw.githubusercontent.com/bootstrapthemesco/bootstrap-4-multi-dropdown-navbar/beta2.0/css/bootstrap-4-navbar.css: Connect timeout
Could not find input asset "https://raw.githubusercontent.com/bootstrapthemesco/bootstrap-4-multi-dropdown-navbar/beta2.0/css/bootstrap-4-navbar.css". at /usr/lib/perl5/vendor_perl/5.36.0/Mojolicious/Plugin/AssetPack.pm line 172.
openQA is licensed GPL-2.0 - Version 4.6.1671708203.c9f8b10
</code></pre>
<p>The openqa-investigate retry jobs passed so sporadic download issue</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> the openQA asset handling ensures that temporary network issues "Connect timeout" are handled with retrying</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>We can probably do some retrying on download issues</li>
<li>Check the code in the AssetPack Mojolicious plugin. As necessary propose upstream solution, as alternative handle with some hard-core log parsing in downstream and just retry :)</li>
</ul>
openQA Project - action #95995 (Resolved): [sporadic][openqa-in-openqa] Test openqa_from_git eve...https://progress.opensuse.org/issues/959952021-07-26T08:51:35Zilausuchilausuch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>In this test run <a href="https://openqa.opensuse.org/tests/1857293#step/openqa_webui/33" class="external">https://openqa.opensuse.org/tests/1857293#step/openqa_webui/33</a> the is a problem. Seems that the server is not responsive</p>
<pre><code># Test died: command 'while ! [ -f nohup.out ]; do sleep 1 ; done && grep -qP "Listening at.*(127.0.0.1|localhost)" <(tail -f -n0 nohup.out) ' timed out at openqa//tests/install/openqa_webui.pm line 68.
</code></pre>
<p><a href="https://openqa.opensuse.org/tests/1857293/logfile?filename=openqa_webui-openqa_nohup_out.txt" class="external">https://openqa.opensuse.org/tests/1857293/logfile?filename=openqa_webui-openqa_nohup_out.txt</a> shows</p>
<pre><code>[warn] [AssetPack] Unable to download https://cdnjs.cloudflare.com/ajax/libs/chosen/1.7.0/chosen.css: Connect timeout
Could not find input asset "https://cdnjs.cloudflare.com/ajax/libs/chosen/1.7.0/chosen.css". at /usr/lib/perl5/vendor_perl/5.32.1/Mojolicious/Plugin/AssetPack.pm line 172.
</code></pre>
<p>which <em>maybe</em> is causing the problem, maybe not.</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 above timeout does not appear again in at least 10 consecutive rounds</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Crosscheck in a passed test if the asset connect timeout warning also shows up to prevent us following a "red herring"</li>
<li>DONE: Check if the above download URL from asset definitions can work -> the link <a href="https://cdnjs.cloudflare.com/ajax/libs/chosen/1.7.0/chosen.css" class="external">https://cdnjs.cloudflare.com/ajax/libs/chosen/1.7.0/chosen.css</a> works</li>
<li>Try to reproduce locally as well as use <a href="https://progress.opensuse.org/projects/openqatests/wiki/Wiki#Statistical-investigation" class="external">https://progress.opensuse.org/projects/openqatests/wiki/Wiki#Statistical-investigation</a> to get statistics of failures</li>
<li>Prevent timeout either on low-level, e.g. asset preparation or high-level, e.g. retry within the openQA-in-openQA tests</li>
</ul>