openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-10-03T08:41:09ZopenSUSE Project Management Tool
Redmine qe-yam - action #41948 (Rejected): [functional][y] New test for formatting/mounting/encrypting a ...https://progress.opensuse.org/issues/419482018-10-03T08:41:09Zancorgsancor@suse.com
<p>The YaST partitioner now allows to "edit" a whole disk with no partitions. See <a href="https://github.com/yast/yast-storage-ng/pull/752" class="external">https://github.com/yast/yast-storage-ng/pull/752</a> for more details.</p>
<p>It would be good to have an openQA test for that.</p>
<p>Possibilities are:</p>
<ul>
<li>to use lvm with partitionless disk</li>
<li>we have autoyast installations using this feature, so we can use those images and run Expert Partitioner and edit existing setup</li>
</ul>
<p>RAID with partitionless disks are out of scope here, as feature is marked as experimental.</p>
<p>See <code>lvm-encrypt-separate-boot</code> as a base</p>
<p>Scope is qemu backend only.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ol>
<li>Installation should use Modify menu which is available when Hard disks is selected in the tree</li>
<li>Installation one partition and one partitionless disk for lvm and is optionally encrypted</li>
<li>Partitioning is validated in the end of installation</li>
</ol>
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 #41276 (Resolved): [functionality][y][research] Test partitions on an MD RAIDhttps://progress.opensuse.org/issues/412762018-09-19T11:40:52Zancorgsancor@suse.com
<p>Now it's possible to manage partitions within a software MD RAID. As part of the change, the interface for managing RAIDs and the distribution of some buttons has changed slightly.</p>
<ul>
<li>In the table of the section "RAIDs" the set of buttons at the bottom change based on the selected row</li>
<li>After creating a new RAID, it does not automatically start the workflow to "edit" it (format and so on)</li>
<li>When clicking on a RAID, it jumps to its new view with tabs "Overview", "Used Devices" and "Partitions"</li>
<li>The buttons for creating a new partition table and for cloning it to another device has been relocated/renamed</li>
</ul>
<p>For more details see:</p>
<ul>
<li><a href="https://trello.com/c/itizMqBG/" class="external">https://trello.com/c/itizMqBG/</a> (and the linked epic card)</li>
<li><a href="https://github.com/yast/yast-storage-ng/pull/737" class="external">https://github.com/yast/yast-storage-ng/pull/737</a></li>
<li><a href="https://github.com/yast/yast-storage-ng/pull/738" class="external">https://github.com/yast/yast-storage-ng/pull/738</a></li>
</ul>
<p>More changes in the locations of the buttons are expected soon. See the discussion at<br>
<a href="https://gist.github.com/ancorgs/bf81a230e2a4634df7a05b90a1241116#file-partitioner-buttons-md" class="external">https://gist.github.com/ancorgs/bf81a230e2a4634df7a05b90a1241116#file-partitioner-buttons-md</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ol>
<li>Draft test plan for the feature is created</li>
<li>Follow-up ticket for automation is created if makes sense</li>
</ol>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ol>
<li>Plain partitions on raid 0,1,10,5,6 (btrfs for /, swap, separate /boot, /home)</li>
<li>lvm on top of raid for different raid levels</li>
<li>encrypted partitions on top of raid</li>
<li>encrypted lvm on top of raid</li>
<li>cloning partitions using expert partitioner</li>
<li>creating 1-4 in the installed system</li>
<li>system cloning with 1-4</li>
<li>autoyast installation with 1-4</li>
</ol>
<p>We have automated test which creates single partition on raid device. Feature is available starting from SLE/Leap 15 SP1, and TW</p>
openQA Tests - action #40682 (Resolved): [functional][y] full disk as LVM PVhttps://progress.opensuse.org/issues/406822018-09-06T13:21:31Zancorgsancor@suse.com
<p>In the partitioner is possible to create an LVM VG on top of partitions and disks (without partition table) alike. I'm not sure if we have a test-case using that functionality or if all our tests define the LVM always based on partitions.</p>
<p>If we don't have it, it would be nice to add it.</p>
<p>Automation is out of scope of the ticket, we should create follow up ticket, we have AY test on 64 bit already, as of now this is already good. But we should come up with some scenario which would be beneficial to automate.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ol>
<li>Functionality is tested manually using TW, Leap 15.1, SLE 15 SP1 which contain changes</li>
<li>Draft test plan for the feature is created</li>
<li>Follow up ticket for the automated test is created depending on the outcome of the test plan</li>
</ol>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<p>Things to test and not limited to:</p>
<ol>
<li>Partitionless physical volume with btrfs</li>
<li>Partitionless physical volume with ext4</li>
<li>volume group on multiple partitons</li>
<li>volume group on multiple disks</li>
<li>1-4 with encrypted lvm (for VG)</li>
<li>1-4 with encrypted lvm and encrypted partitions in VG</li>
<li>VG with a disk and lvm partition</li>
<li>Activation of the disk partitions by installer when having a disk with installations from 1-7</li>
<li>At least perform one autoyast re-installation (install -> clone system -> install using created profile), use testing strategies here not to repeat this step for 1-8</li>
<li>Whole disk as a single partition</li>
<li>Special disks (DASD, ZFCP, iSCSI)</li>
<li>Repeat some of the suggestions using Expert Partitioner in the installed system</li>
</ol>
<p>AY scenario is already automated: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&version=15-SP1&machine=64bit&test=autoyast_disk_as_pv&distri=sle&flavor=Installer-DVD" class="external">https://openqa.suse.de/tests/latest?arch=x86_64&version=15-SP1&machine=64bit&test=autoyast_disk_as_pv&distri=sle&flavor=Installer-DVD</a><br>
But it's only 64bit, worth checking on other setups.</p>
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>
openSUSE admin - tickets #9792 (Resolved): Lizards account for YaST Teamhttps://progress.opensuse.org/issues/97922015-12-03T12:44:50Zancorgsancor@suse.com
<p>The YaST team has decided that it would be good to publish (the most sexy part of) our sprint review results in lizards, to make YaST development more visible.</p>
<p>The team already has an iChain account with the username yast-team</p>
<p>Would it be possible to have a lizards account associated to it?</p>
openSUSE admin - tickets #9284 (Closed): New SLE12 VM to substitute software.opensuse.orghttps://progress.opensuse.org/issues/92842015-10-20T14:14:10Zancorgsancor@suse.com
<p>We want to replace the machine currently hosting software.o.o (proxy-opensuse.suse.de:2227) with a new SLE12 host.</p>
<p>There are tons of authorized keys in the current machine, but I believe that lately only coolo and myself are taking care (for some definition of "take care"). You can take our keys from the old machine (<a href="mailto:coolo@kde.org">coolo@kde.org</a> and ags@azuquahe). Feel free to also copy any other key you think is worth it.</p>
<p>We don't have the full deployment automated, but at least we have an rpm to deploy updates of the website. I'll document every step so we can hopefully create a puppet recipe for the future.</p>
openQA Project - action #8542 (Resolved): Staging openQA instanceshttps://progress.opensuse.org/issues/85422015-08-19T07:23:55Zancorgsancor@suse.com
<p>Recently, some breakage has been introduced in openqa.opensuse.org by externally contributed tests ("externally" meaning me in this case ;-) ). External contributors cannot afford to verify the test in all the scenarios run by openqa.opensuse.org, so this will happen in the future again. It would be useful to use tortuga or any other machine to run a subset of the scenarios run in the official instance to make sure the new tests can be deployed with some degree of confidence.</p>
openQA Project - action #8540 (New): Easier workflow to submit needles for casual contributorshttps://progress.opensuse.org/issues/85402015-08-19T07:19:55Zancorgsancor@suse.com
<a name="User-stories"></a>
<h2 >User stories<a href="#User-stories" class="wiki-anchor">¶</a></h2>
<ul>
<li>US1: As a test developer / reviewer changing needles I want my proposed needle changes to be reviewed to let others review my changes</li>
<li>US2: As a meta-reviewer I can see who changed needles when and why to distinguish different test failure causes</li>
</ul>
<a name="US1-TODO"></a>
<h2 >US1: TODO<a href="#US1-TODO" class="wiki-anchor">¶</a></h2>
<a name="US2-Comment-for-changes-in-needle-editor"></a>
<h2 >US2: Comment for changes in needle editor<a href="#US2-Comment-for-changes-in-needle-editor" class="wiki-anchor">¶</a></h2>
<a name="acceptance-criteria"></a>
<h3 >acceptance criteria<a href="#acceptance-criteria" class="wiki-anchor">¶</a></h3>
<ul>
<li>a comment window in the needle editor is available</li>
<li>the entered comment is added in the auto-created git commit</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Original story from ancorgs:<br>
During a recent meeting we discussed the possibility of making easier for casual contributors to submit needles, maybe allowing direct submissions from other openQA instances. Just something to think about for the time being.</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>
openSUSE admin - tickets #7456 (Closed): Access to connect API from boosters (TSP app)https://progress.opensuse.org/issues/74562015-05-11T13:20:09Zancorgsancor@suse.com
<p>The TSP app (hosted in boosters) needs access to the connect.o.o RESTful API, right now, a GET request like this executed from boosters gets a connection refused error.<br>
<a href="https://connect.opensuse.org/services/api/rest/json?api_key=XXX&attribute=*&login=whoever&method=connect.user.attribute.get" class="external">https://connect.opensuse.org/services/api/rest/json?api_key=XXX&attribute=*&login=whoever&method=connect.user.attribute.get</a></p>
openQA Project - action #6414 (Rejected): Meaningful and understandable productshttps://progress.opensuse.org/issues/64142015-02-25T11:55:23Zancorgsancor@suse.com
<p>We need a good way to group jobs (and thus results) in the dashboards for QA. That's intuitively, different products like "Tumbleweed", "Default SLES12", "SLES12 for s390".</p>
<p>Right now the term "product" is used in openQA just as a mechanism to match isos to job templates. From the official documentation[1]: "a product in openQA is a simple description without any concrete meaning". They are even volatile, i.e. expected to change as the time goes by without any relevant consequence in the already created jobs.</p>
<p>Right now, a product is used to match isos by:</p>
<ul>
<li>distri (relevant also to choose one set of tests/needles or another)</li>
<li>version (like "SLE11-SP4" or "SLE12")</li>
<li>flavor (like "DVD" or "Rescue CD")</li>
<li>arch (like "i586" or "x86_64")</li>
</ul>
<p>[1] <a href="https://github.com/os-autoinst/openQA/blob/master/docs/GettingStarted.asciidoc#using-job-templates-to-automate-jobs-creation" class="external">https://github.com/os-autoinst/openQA/blob/master/docs/GettingStarted.asciidoc#using-job-templates-to-automate-jobs-creation</a></p>
openQA Project - action #6058 (Resolved): Run migrations with the right user in the packagehttps://progress.opensuse.org/issues/60582015-01-27T10:06:48Zancorgsancor@suse.com
<p>Make sure migrations are run with the geekotest user in the package, so it works with both SQLite and PostgreSQL using "peer" as authentication method.</p>