openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-06-05T10:41:39ZopenSUSE Project Management Tool
Redmine openQA Tests - action #67768 (Resolved): [kernel][hpc] SLE15-SP2 GMC HPC exploratory checkshttps://progress.opensuse.org/issues/677682020-06-05T10:41:39Zsebchladsebastian.chlad@suse.com
<p>This should commence with GMC build</p>
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 Tests - action #64039 (Resolved): test fails in slurm_masterhttps://progress.opensuse.org/issues/640392020-03-02T08:45:40Zsebchladsebastian.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_DELTA_slurm_master_accounting@64bit fails in<br>
<a href="https://openqa.suse.de/tests/3939585/modules/slurm_master/steps/313" 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. 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/3936274" class="external">146.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/3922312" class="external">143.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_DELTA_slurm_master_accounting&version=15-SP2" class="external">latest</a></p>
<p>Longer Story:<br>
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1165151" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1165151</a><br>
<a href="https://jira.suse.com/browse/SLE-9356" class="external">https://jira.suse.com/browse/SLE-9356</a></p>
<p>One would assume better tests for the DB should be in place however HPC tests are not really meant to do that. HPC tests are there to ensure checks of the HPC components. </p>
<p>I will try to encourage Marita/QA SLE Pro Man to ensure better functional tests of the DB.</p>
openQA Tests - action #62858 (Resolved): [kernel][hpc] test fails in slurm_masterhttps://progress.opensuse.org/issues/628582020-01-31T12:44:09Zsebchladsebastian.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_ALPHA_slurm_master@64bit fails in<br>
<a href="https://openqa.suse.de/tests/3849070/modules/slurm_master/steps/89" 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>Simple HPC cluster with 1 slurmctl and multiple compute nodes Maintainer : <a href="mailto:schlad@suse.de">schlad@suse.de</a> , <a href="mailto:pcervinka@suse.com">pcervinka@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/3791496" class="external">122.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/3785815" class="external">122.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_ALPHA_slurm_master&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #62645 (Resolved): [hpc] test hpchttps://progress.opensuse.org/issues/626452020-01-24T13:52:24Zsebchladsebastian.chlad@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>HPC test should work.</p>
<p>fix hpc test lib</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 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 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 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>