openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-01-15T08:33:08ZopenSUSE Project Management Tool
Redmine openQA Tests - action #62153 (Resolved): [hpc] test fails in slurm_masterhttps://progress.opensuse.org/issues/621532020-01-15T08:33:08Zsebchladsebastian.chlad@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Online-aarch64-hpc_GAMMA_slurm_master_db@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/3787688/modules/slurm_master/steps/14" class="external">slurm_master</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Slurm accounting tests with db configured and NFS shared folder provided. 2 ctls, multiple compute nodes. Maintainer: schlad</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/3758774" class="external">120.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/3729513" class="external">105.4</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=aarch64&distri=sle&flavor=Online&machine=aarch64&test=hpc_GAMMA_slurm_master_db&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #60731 (Resolved): [hpc] test fails in before_testhttps://progress.opensuse.org/issues/607312019-12-05T13:21:36Zsebchladsebastian.chlad@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Online-aarch64-hpc_ALPHA_mpich_mpi_master@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/3666210/modules/before_test/steps/53" class="external">before_test</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Basic tests of mpich with CPU count=1. Maintainer: schlad <a href="mailto:schlad@suse.de">schlad@suse.de</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/3618154" class="external">92.1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: (unknown) (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Online&machine=aarch64&test=hpc_ALPHA_mpich_mpi_master&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #60728 (Resolved): [hpc] test fails in setuphttps://progress.opensuse.org/issues/607282019-12-05T13:11:43Zsebchladsebastian.chlad@suse.com
<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_BETA_slurm_adv_supportserver@64bit fails in<br>
<a href="https://openqa.suse.de/tests/3663349/modules/setup/steps/40" class="external">setup</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>HPC cluster with 2 slurm ctls and multiple compute nodes. NFS folder mounted for slurmctls, so the failover can be tested<br>
Maintainer: <a href="mailto:schlad@suse.de">schlad@suse.de</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/3614243" class="external">92.1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: (unknown) (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=hpc_BETA_slurm_adv_supportserver&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #52256 (Resolved): [hpc][kernel] Prepare support_server NFS serverhttps://progress.opensuse.org/issues/522562019-05-28T15:23:00Zsebchladsebastian.chlad@suse.com
<p>Some HPC tests require to use NFS server, as the 2 nodes could share one directory.</p>
<p>Currently I use custom test run() for this but implementing this in support_server (as there is a flag for it) would be desirable</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 #30237 (Resolved): [hpc] single package tests for HPC SLE15 should be enabl...https://progress.opensuse.org/issues/302372018-01-12T09:34:46Zsebchladsebastian.chlad@suse.com
<p>This task should be handled after polishing some current tests. Make not much sense - as Anton rightly suggested - to enable broken tests for ARM.</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 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 Tests - action #12288 (Resolved): [test review] snapper_undochange fails to create first s...https://progress.opensuse.org/issues/122882016-06-10T11:59:00Zsebchladsebastian.chlad@suse.com
<a name="observation"></a>
<h2 >observation<a href="#observation" class="wiki-anchor">¶</a></h2>
<p>test fails for no apparent reason so indication is that it might be openQA performance limitations</p>
<a name="reproducible"></a>
<h2 >reproducible<a href="#reproducible" class="wiki-anchor">¶</a></h2>
<p>occured at least twice: </p>
<a name="problem"></a>
<h2 >problem<a href="#problem" class="wiki-anchor">¶</a></h2>
<p>H1. test timeout of 30 seconds is too strict to ensure a snapshot can be created under all circumstances<br>
H2. a snapshot sometimes can not be created at all, waiting for longer would not help<br>
H3. ppc64le specific</p>
<a name="suggestion"></a>
<h2 >suggestion<a href="#suggestion" class="wiki-anchor">¶</a></h2>
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 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 Tests - action #12110 (Resolved): gnome_control_center: short timeout on details caused te...https://progress.opensuse.org/issues/121102016-05-24T14:01:52Zsebchladsebastian.chlad@suse.com
<a name="observation"></a>
<h2 >observation<a href="#observation" class="wiki-anchor">¶</a></h2>
<p>gnome_control_center fails as there is no details displayed as expected, e.g. see <a href="https://openqa.suse.de/tests/396384" class="external">https://openqa.suse.de/tests/396384</a></p>
<a name="problem"></a>
<h2 >problem<a href="#problem" class="wiki-anchor">¶</a></h2>
<p>It seems like in staging we see issue with short timeout set to 3 so the the needle does not match to the expected results.</p>
<a name="suggestions"></a>
<h2 >suggestions<a href="#suggestions" class="wiki-anchor">¶</a></h2>
<ol>
<li><p>perhaps increase the timeout however that is a bad solution.</p></li>
<li><p>should we monitor system resources to get the better picture instead of just increasing timeouts?</p></li>
</ol>