openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-10-03T08:39:42ZopenSUSE Project Management Tool
Redmine openQA Tests - action #41945 (Resolved): [functional][y] Adapt the test to the new UI of the part...https://progress.opensuse.org/issues/419452018-10-03T08:39:42Zancorgsancor@suse.com
<p>In order to accommodate all the new functionality of the Partitioner (like the possibility of creating partitions within a RAID or to format a disk directly with no partition table), we had to redesign a little bit the UI of the partitioner.</p>
<p>The new UI, with a set of menu-buttons that group functionality and changes based on the selected row in the upper table, is explained here <a href="https://github.com/yast/yast-storage-ng/pull/752" class="external">https://github.com/yast/yast-storage-ng/pull/752</a></p>
<p>The description of that PR also contains a link to the document explaining the rationale behind the change.</p>
<p>All openQA test using the Partitioner must be adapted to use the new UI.</p>
openQA Tests - action #41876 (Resolved): [sle][functional][y][feature:dev:done][timeboxed:8h] jsc...https://progress.opensuse.org/issues/418762018-10-01T16:10:46Zancorgsancor@suse.com
<p>Starting with yast2-storage-ng 4.1.21, it's possible to create new bcache devices with the Expert Partitioner. It would be nice to have some test for it.</p>
<p>More information at <a href="https://trello.com/c/BnP4shXJ/308-3-fate-325346-create-bcache-devices" class="external">https://trello.com/c/BnP4shXJ/308-3-fate-325346-create-bcache-devices</a></p>
<p><a href="https://lizards.opensuse.org/2019/02/27/yast-sprint-71-72/" class="external">https://lizards.opensuse.org/2019/02/27/yast-sprint-71-72/</a></p>
<p><a href="https://jira.suse.de/browse/SLE-3170" class="external">epic</a><br>
<a href="https://jira.suse.de/browse/SLE-4329" class="external">dev task</a><br>
<a href="https://jira.suse.de/browse/SLE-4525" class="external">QA task</a></p>
<a name="Suggestions-to-test"></a>
<h2 >Suggestions to test<a href="#Suggestions-to-test" class="wiki-anchor">¶</a></h2>
<ol>
<li>Test on other architectures with bcache not well supported (any except x86_64)</li>
<li>Test with encrypted partitions on bcache</li>
<li>Test with LVM on bcache</li>
<li>Test encrypted LVM with bcache</li>
<li>Test re-installation with partitions from 2-4</li>
<li>Test autoyast installations for 2-5</li>
<li>Combine different bcache configurations during these scenarios (e.g. no caching device)/</li>
<li>Test partitioner in the installed system.</li>
</ol>
openQA Tests - action #40679 (Rejected): [functional][y] whole disk as part of an MD RAIDhttps://progress.opensuse.org/issues/406792018-09-06T13:19:49Zancorgsancor@suse.com
<p>This pull request adds the possibility to the partitioner of defining an MD RAID array on top of full disks, not only on top of partitions. <a href="https://github.com/yast/yast-storage-ng/pull/726" class="external">https://github.com/yast/yast-storage-ng/pull/726</a></p>
<p>It would be nice to have a test probing that it actually works. For example, combining a disk and a partition in the same RAID.</p>
openQA Tests - action #40676 (Resolved): [functional][y] Adapt to the new workflow of "Create New...https://progress.opensuse.org/issues/406762018-09-06T13:18:07Zancorgsancor@suse.com
<p>See more details at <a href="https://github.com/yast/yast-storage-ng/pull/726" class="external">https://github.com/yast/yast-storage-ng/pull/726</a></p>
openQA Project - action #8538 (Closed): Comment (and refactor if possible) main.pmhttps://progress.opensuse.org/issues/85382015-08-19T07:17:31Zancorgsancor@suse.com
<p>To easy contribution of new tests, a more understandable main.pm is needed so people not familiar with openqa.(suse.de/opensuse.org) can introduce new tests in the right place.</p>
<p><a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/7c9885ef167a5e853a36bb0100490704258a0dee" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/7c9885ef167a5e853a36bb0100490704258a0dee</a> is already a step in the right direction.</p>
openQA Project - action #5852 (Resolved): Remove dependency from DBIx::Class::Schema::Config and ...https://progress.opensuse.org/issues/58522015-01-13T10:25:27Zancorgsancor@suse.com
<p>DBIx::Class::Schema::Config is actually only used to load database configurations from database.ini. It uses Config::Tiny for parsing the file. We already use Config::IniFiles, which is way more powerful than Config::Tiny, for parsing other ini files. We can get rid of 2 dependencies and improve .ini parsing with just some lines of Perl code.</p>
openQA Project - action #2608 (Resolved): More robust alternative to upload_logshttps://progress.opensuse.org/issues/26082014-06-02T12:11:40Zancorgsancor@suse.com
<p>There are several situations in which an incomplete test fails before calling upload_logs, making debugging harder. We need a more robust alternative.</p>
openQA Project - action #2246 (Resolved): Consistent vocabularyhttps://progress.opensuse.org/issues/22462014-04-04T11:34:09Zancorgsancor@suse.com
<p>For historical reason, "test" means a lot of things (and nothing at the same time) in openQA. In the webUI it means "job". In the API is not used. Internally is both a job attribute and a special job_setting which is always present and equal to the job attribute. In the meantime, we introduced a new word "TestSuite" to avoid reusing "test" one more time.</p>
<p>In my opinion.</p>
<ul>
<li>We should start using "job" everywhere for... well, for the jobs. Removing the current "tests/xx" urls.</li>
<li>TestSuite should be renamed to Test. Now that even the internal job_setting called TEST and the job attribute are always set to the name of the TestSuite, it looks like we finally have a clear definition of what a "test" is.</li>
</ul>
openQA Project - action #2218 (Resolved): idea: Merge /admin/workers view with the running table ...https://progress.opensuse.org/issues/22182014-04-03T11:45:12Zancorgsancor@suse.com
<p>The workers view should not be a full view (which we don't even know where to place the link to, btw), but substitute one of the "not implemented yet" boxes in the front page. Using AJAX, I would say.</p>
openQA Project - action #2214 (Resolved): Better management of ENV variables on job_templateshttps://progress.opensuse.org/issues/22142014-04-03T11:36:09Zancorgsancor@suse.com
<p>Right now, products, machines and test_suites can define environment variables. But those list of variables are only a string that is parsed. That can be improved in several ways:</p>
<ul>
<li>We need to be careful about what we accept as variable names in the web ui. Since those settings are exported to the environment things like e.g LD_PRELOAD must not be allowed. Maybe we should rename all variables to start with OPENQA_ or something similar to avoid side effects in the first place.</li>
<li>Create the key / value separation of variables, as was done in job_settings table</li>
<li>Drive / limit / control the options that the user have in the UI side (DESKTOP \in {KDE, GNOME, XFCE, LXDE})</li>
</ul>
<p>We have to decide where we want to go exactly and then implement it.</p>
openQA Project - action #1810 (Rejected): Revamp opensuseqa.suse.de installationhttps://progress.opensuse.org/issues/18102014-03-06T14:39:37Zancorgsancor@suse.com
<p>As a "dress rehearsal" for final deploy, we should probably install SLE11SP3+openQA in opensuseqa.opensuse.org, fixing every issue that pops up with the package, the AppArmor profile, authentication, workers going crazy...</p>
openQA Project - action #1806 (Rejected): Packages for SLE11https://progress.opensuse.org/issues/18062014-03-06T14:30:58Zancorgsancor@suse.com
<p>We need openQA packages for SLE11 (SP3?) in order to integrate the new version in the existing servers infrastructure.</p>
openQA Project - action #1729 (Resolved): iChain integrationhttps://progress.opensuse.org/issues/17292014-02-25T14:47:24Zancorgsancor@suse.com
<p>At some point, it will be useful to match the users in openQA DB with the users of the openSUSE infrastructure using iChain. Hopefully as a generic reusable plugin for Mojolicious.</p>
openQA Project - action #1636 (Resolved): Moves useful scripts from 'tools' to 'script'https://progress.opensuse.org/issues/16362014-02-20T09:32:37Zancorgsancor@suse.com
<p>All new scripts (like the application itself, the new worker, etc.) are in the directory called 'script'. The one called 'tools' should be deprecated. Everything which is still useful should be moved, the rest should die with the directory. In addition, I would suggest to rename 'script' into 'bin', but that is just a matter of taste.</p>
openQA Project - action #1415 (Resolved): Cache image thumbnailshttps://progress.opensuse.org/issues/14152014-02-06T08:59:49Zancorgsancor@suse.com
<p>openQA constantly generates thumbnails of images to send to the browser, but the result of the resize is not cached as a file server-side. Not very efficient.</p>
<p>As always, tests needed.</p>