openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-05-15T11:41:55ZopenSUSE Project Management Tool
Redmine openQA Tests - action #66907 (Rejected): Multimachine test fails in setup for ARM workershttps://progress.opensuse.org/issues/669072020-05-15T11:41:55Zsebchladsebastian.chlad@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>With RC2 build for SLE15SP2 we hit again known ARM MM problems. Those are recurring issues and require usual attention form QA tools team/people with access to OSD machines.<br>
As this is RC2 build validation day, I'm opening this to perhaps get some traction on finding long term solutions. </p>
<p>openQA test in scenario sle-15-SP2-Online-aarch64-hpc_DELTA_slurm_accounting_supportserver@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/4236631/modules/setup/steps/72" 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>Slurm accounting tests with db configured and NFS shared folder provided. 1 ctl, 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/4236631" class="external">194.1</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.suse.de/tests/4230231" class="external">191.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=aarch64&distri=sle&flavor=Online&machine=aarch64&test=hpc_DELTA_slurm_accounting_supportserver&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 Project - action #52517 (Rejected): Sorting out tests: Visualize parallel job dependencies...https://progress.opensuse.org/issues/525172019-06-03T15:14:01Zsebchladsebastian.chlad@suse.com
<p>The current openQA webUI seems sorting out elements (tests) alphabetically.<br>
For instance: <a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=228.2&groupid=130" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=228.2&groupid=130</a></p>
<p>In the meantime, Marius implemented the feature of displaying dependencies within a test run.<br>
<a href="https://openqa.suse.de/tests/2923320#dependencies" class="external">https://openqa.suse.de/tests/2923320#dependencies</a></p>
<p>I'm introducing more tests for cluster testing, so there are multiple VMs (cluster nodes) which are displayed as separate 'tests' while in fact those are VMs constituting multi-node test run.<br>
The current webUI does not provide a nice way to display such tests in a way which would be easy for people to recognize it.</p>
<p>I wonder if there is a quick way to take advantage of Marius' work and be able to render the page of a job group for a given build in way to group certain tests together.</p>
<p>Of course this could be achieved by proper naming, but this still seems like a workaround and not a proper solution. </p>
<p>I wonder if people see similar need and if there are any ideas on how to go about this use case.</p>
openQA Project - action #51932 (Resolved): Trimming of white spaces on "machine definition"https://progress.opensuse.org/issues/519322019-05-23T14:22:56Zsebchladsebastian.chlad@suse.com
<p>As it looks there is no trimming of leading white space characters which might result in fairly obscure problems with - for instance - scheduler picking up the jobs.</p>
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 Project - action #32593 (Rejected): Multiple ttySx consoles for qemuhttps://progress.opensuse.org/issues/325932018-03-01T11:56:43Zsebchladsebastian.chlad@suse.com
<p>For some testing it could be useful to have a possibility to create some more ttyS devices.</p>
<p>Would it be useful to have another variable, say MSERIALDEV, where test writer could specify how many ttyS devices he or she needs?</p>
<p>Or would it be better to play with SERIALDEV, so it could do the job of starting more than one ttyS devices?</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 #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 #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 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>