openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-03-05T09:08:10ZopenSUSE Project Management Tool
Redmine openQA Tests - action #64243 (Resolved): test fails in mrsh_masterhttps://progress.opensuse.org/issues/642432020-03-05T09:08:10Zsebchladsebastian.chlad@suse.com
<p>See:<br>
add SET_CUSTOM_PROMPT=1 it's <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9100/files" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9100/files</a></p>
<pre><code>github.com
Save time by not setting custom prompt in shell sessions anymore by okurz · Pull Request #9100 · os-autoinst/os-autoinst-distri-opensuse
Some years ago when tests were requiring more screen checks even for basic operations we set a different prompt to make needles easy to maintain. By now this should not be necessary anymore but has...
</code></pre>
<p>===</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Online-x86_64-hpc_mrsh_master@64bit fails in<br>
<a href="https://openqa.suse.de/tests/3957826/modules/mrsh_master/steps/16" class="external">mrsh_master</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:mgriessmeier@suse.com">mgriessmeier@suse.com</a>, <a href="mailto:pcervinka@suse.com">pcervinka@suse.com</a>, <a href="mailto:asmorodskyi@suse.com">asmorodskyi@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/3951978" class="external">150.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/3939563" class="external">148.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=Online&machine=64bit&test=hpc_mrsh_master&version=15-SP2" class="external">latest</a></p>
openQA Infrastructure - action #54698 (Rejected): Worker7 - network problemshttps://progress.opensuse.org/issues/546982019-07-26T15:17:09Zsebchladsebastian.chlad@suse.com
<p>so as we talked; whenever mm job is hitting worker7, the test fails.</p>
<p>i.e.<br>
Refreshing service 'Web_and_Scripting_Module_12_x86_64'.<br>
Download (curl) error for '<a href="https://updates.suse.com/SUSE/Updates/SLE-Module-HPC/12/x86_64/update/repodata/repomd.xml?MogMv4ezT369G0BXqqyitOJNZ0_AekQF5tMfiSgaqP67bBMA-4XlnoKmcH2y7ZxeB45ifnmiF1XVCGXsJMwhLcE7-ynUa0fMaOuUoisW7D1FRPoGewjAqOcEGW9CjEU5VES17JLw_utbVTI':" class="external">https://updates.suse.com/SUSE/Updates/SLE-Module-HPC/12/x86_64/update/repodata/repomd.xml?MogMv4ezT369G0BXqqyitOJNZ0_AekQF5tMfiSgaqP67bBMA-4XlnoKmcH2y7ZxeB45ifnmiF1XVCGXsJMwhLcE7-ynUa0fMaOuUoisW7D1FRPoGewjAqOcEGW9CjEU5VES17JLw_utbVTI':</a><br>
Error code: Connection failed<br>
Error message: Could not resolve host: updates.suse.com</p>
<p>This is on:<br>
Assigned worker: openqaworker7:16 </p>
<p>I saw supportserver using worker7 and then there is no traffic going on.</p>
<p>All in all I reckon firewall mis-configuration.</p>
openQA Tests - action #34576 (New): [sssd][ldap][migration][network] Implement functional testing...https://progress.opensuse.org/issues/345762018-04-09T15:03:53Zsebchladsebastian.chlad@suse.com
<p>The basic idea is to test migration more widely by re-using migration openQA modules in different areas so - for instance - some network services could be installed and configured on earlier version of SLES, then migration openQA module could be "called", the migration to a given SLES version could be done, and eventually we could see if pre-configured service is still working.</p>
<p>Suggested by SLE Architect - Thorsten K. - for his preferences.</p>
<ul>
<li>setup openldap server with YaST module</li>
<li>setup ldap client (sssd)</li>
<li>setup autorization against Windows domain server</li>
</ul>
<p>The target for this is SLE12 SP4.</p>
openQA Tests - action #27826 (Rejected): [functional][opensuse][u] Prepare simple ON/OFF test for...https://progress.opensuse.org/issues/278262017-11-17T09:53:09Zsebchladsebastian.chlad@suse.comopenQA Tests - action #18326 (New): [sle15sp4][desktop] regression-firefox test relies on externa...https://progress.opensuse.org/issues/183262017-04-04T11:19:50Zsebchladsebastian.chlad@suse.com
<p>The point to improved, as suggested by rbrown: <br>
Test-Module: /var/lib/openqa/share/tests/sle/tests/x11regressions/firefox/sle12/firefox_extcontent.pm </p>
<p>Instead of relying on <br>
my $ext_link = "<a href="http://mirror.bej.suse.com/dist/install/SLP/SLE-12-Server-GM/x86_64/dvd1/" class="external">http://mirror.bej.suse.com/dist/install/SLP/SLE-12-Server-GM/x86_64/dvd1/</a>";<br>
test could use openQA internal resources.</p>
openQA Tests - action #12758 (Resolved): Reboot gnome scenario failshttps://progress.opensuse.org/issues/127582016-07-19T13:18:55Zsebchladsebastian.chlad@suse.com
<p>Please see following: <a href="https://openqa.suse.de/tests/479007#step/reboot_gnome/8" class="external">https://openqa.suse.de/tests/479007#step/reboot_gnome/8</a></p>
<p>Logs does not indicate well enough what could possibly go wrong. One could see events like right-click present. Seems like correct place on the screen however reboot is not happening.</p>
<p>This should be investigated further as I can't conclusively state if this is openQA issue or perhaps product bug.</p>
openQA Project - action #12340 (Rejected): [infrastructure] Can't write to asset: No space left https://progress.opensuse.org/issues/123402016-06-14T14:41:14Zsebchladsebastian.chlad@suse.com
<p>Mojo::Reactor::Poll: I/O watcher failed: Can't write to asset: No space left on device at /usr/lib/perl5/vendor_perl/5.18.2/Mojo/Asset/Memory.pm line 18.</p>
openQA Tests - action #12338 (Resolved): [improvement] sending TERM to qemu pidhttps://progress.opensuse.org/issues/123382016-06-14T12:39:03Zsebchladsebastian.chlad@suse.com
<p>We have a test on ppc64le which dies.<br>
Error: sending TERM to qemu pid: 49342</p>
<p>We could possibly rerun the test once qemu dies?</p>
<p>I could imagine having automatic label for tests where qemu dies.</p>
openQA Tests - action #12332 (Rejected): [performance] Install and reboot scenarios time out whil...https://progress.opensuse.org/issues/123322016-06-14T12:16:16Zsebchladsebastian.chlad@suse.com
<p>Some tests for ppc64le with reboot fail. type_string is called and then test fails while waiting for serial.</p>
<p>Note that the scenario works most of the time. It happens it failed 2 times recently, so likely some problems on openQA performance side.</p>
openQA Project - action #12292 (Resolved): [test review] Missing assets in openQAhttps://progress.opensuse.org/issues/122922016-06-10T12:54:58Zsebchladsebastian.chlad@suse.com
<p>test fails as assets are missing:<br>
<a href="https://openqa.suse.de/tests/442120#step/consoletest_setup/25" class="external">https://openqa.suse.de/tests/442120#step/consoletest_setup/25</a></p>
openQA Tests - action #12286 (Rejected): [test review] iscsi_client test fails as cmd is typed b...https://progress.opensuse.org/issues/122862016-06-10T11:37:53Zsebchladsebastian.chlad@suse.com
<p>Test Scenario on iscsi_client has a timeout on one step where window should be closed. Window is not closed early enough so the cmd on console is typed to early which causes test to fail.</p>
<p>timeout should be replaced with wait for serial.</p>
openQA Project - action #12180 (New): [webui] Prevent tests to be triggered when required assets ...https://progress.opensuse.org/issues/121802016-05-31T13:17:33Zsebchladsebastian.chlad@suse.com
<a name="User-story"></a>
<h2 >User story<a href="#User-story" class="wiki-anchor">¶</a></h2>
<p>As a unaware user of the webui I do not want to be confused by incomplete tests to save time and not annoy developers learning about the issues.</p>
<a name="acceptance-criteria"></a>
<h2 >acceptance criteria<a href="#acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> Clicking restart button of a job where the required assets do not exist anymore is not possible with a notice to the user about the reason</li>
</ul>
<a name="tasks"></a>
<h2 >tasks<a href="#tasks" class="wiki-anchor">¶</a></h2>
<ul>
<li>first probably we need to define what "required assets" mean</li>
<li>check existance of required asset on retrieving job details</li>
<li>integrate into webUI (user notice preventing retrigger)</li>
<li>integrate into API (return error)</li>
</ul>
<a name="further-details"></a>
<h2 >further details<a href="#further-details" class="wiki-anchor">¶</a></h2>
<p>original content: Once of the openQA tests was triggered despite missing asset. </p>
openQA Tests - action #12176 (Resolved): [test review] SCC registration test scenarios: Registrat...https://progress.opensuse.org/issues/121762016-05-31T12:49:18Zsebchladsebastian.chlad@suse.com
<p>proxy_SCC there is a problem with registration.</p>
openQA Project - action #12104 (Rejected): A user without explicit role can not add comments on o...https://progress.opensuse.org/issues/121042016-05-24T09:07:56Zsebchladsebastian.chlad@suse.com
<a name="observation"></a>
<h2 >observation<a href="#observation" class="wiki-anchor">¶</a></h2>
<p>As a logged in user but without a role assigned in openQA you can not add a comment and get "Forbidden" response</p>
<a name="steps-to-reproduce"></a>
<h2 >steps to reproduce<a href="#steps-to-reproduce" class="wiki-anchor">¶</a></h2>
<ul>
<li>As a user not in the openQA database log in (this is what okurz wrote)</li>
<li>Try to add comment</li>
<li>Observe error response</li>
</ul>
<a name="problem"></a>
<h2 >problem<a href="#problem" class="wiki-anchor">¶</a></h2>
<p>maybe regression</p>
<a name="suggestion"></a>
<h2 >suggestion<a href="#suggestion" class="wiki-anchor">¶</a></h2>
<ul>
<li>Add a proper test</li>
<li>Try with older version</li>
<li>If this is desired behaviour the comment edit window should not be shown at all</li>
</ul>
openQA Project - action #11946 (Resolved): Automatic creation of factory/isohttps://progress.opensuse.org/issues/119462016-05-12T12:26:14Zsebchladsebastian.chlad@suse.com
<a name="user-story"></a>
<h2 >user story<a href="#user-story" class="wiki-anchor">¶</a></h2>
<p>As a developer I would like to have directories structure being created automatically.</p>
<a name="acceptance-criteria"></a>
<h2 >acceptance criteria<a href="#acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>during the first use of clone_job.pl script factory/iso directory should be created automatically</li>
</ul>