openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-09-18T11:20:56ZopenSUSE Project Management Tool
Redmine openQA Infrastructure - action #41189 (Resolved): [tools][monitoring] Worker 'reachable' notifica...https://progress.opensuse.org/issues/411892018-09-18T11:20:56Zsebchladsebastian.chlad@suse.com
<p>As we have initial grafana to monitor the state of machines/workers, we need to start sending email notifications from existing grafana monitoring.</p>
<p>See: <a href="http://docs.grafana.org/alerting/notifications/" class="external">http://docs.grafana.org/alerting/notifications/</a></p>
<p>Requirements:</p>
<ul>
<li>email notifications should be delivered to an open mailing list</li>
<li>QAM and QASLE (Marita and Heiko) are subscribed to those notifications</li>
</ul>
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 #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 #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>
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>