coordination #23340
closed[sle][functional][epic]Adaption to new yast storage stack
100%
Description
The new yast storage stack will be merged to SLE15 shortly. This
will obviously have an impact on QA: All (or almost all) openQA test
cases will break.
There will be various reasons for that:
The UI has changed, needles will not match. We run the tests in our
own infrastructure, I believe that getting the needles and adjusting the
workflows according to them should be relatively easy. I hope that
Christopher can give you access to them, you can see what we already
test at http://pong.suse.czIt is possible that the proposal simply behaves slightly differently,
depending on the disk size and its contents as well as settings (we can
always argue whether the system should omit /home partition or delete
Windows completely to have space for it, just as an example). Those will
need to be reviewed and adapted.There are still some features not implemented yet; this may cover
some installation scenarios, but mainly is about the expert partitioner.
In spite of that, we do not want to delay including it in the code base;
the sooner, the more time we have to discover those issues. And I fully
expect many reports about problems, which we will then need to address
one-by-one. The later we do it, the more painful it will be for everyone.
What we will need relativly quckly is adapting the test cases which are
now run on staging. The team will provide you all needed input and, I
believe, in many cases everything can be taken from our test infrastructure.
Updated by okurz over 6 years ago
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3409 merged as well as needles for openSUSE, let's see in production
Updated by riafarov over 6 years ago
: The storage stack in Staging:Y is now built and installable. You can put your QA hands on it and check OpenQA set-up
http://download.suse.de/ibs/SUSE:/SLE-15:/GA:/Staging:/Y/images/iso/
Updated by riafarov over 6 years ago
There is a bug in yast now, so cannot adjust all tests. First PR for staging: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3465
Updated by okurz over 6 years ago
The changes have been submitted into the product with build 170.1 . Now we see the problems there a lot. Also some failures in the test module "system_role" which was applying a workaround based on a partitioning needle to detect a missing system role, e.g. https://openqa.suse.de/tests/1129483#step/system_role/1
Updated by okurz over 6 years ago
- Priority changed from Normal to Urgent
As the changes were submitted to the product overruling staging we have to see this as urgent as it now blocks many tests. So much for planning…
Updated by riafarov over 6 years ago
Tests adjustments: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3470
Blocked on some bugs, so leave the ticket open to proceed once fixed.
Updated by riafarov over 6 years ago
Verifying lvm-full-encrypt and create_hdd_textmode. For text mode additional needles may be required.
Updated by riafarov over 6 years ago
Test to fix https://openqa.suse.de/tests/1134379#
Updated by mgriessmeier over 6 years ago
issue: unexpected popup during raid configuration:
https://openqa.suse.de/tests/1149401#step/partitioning_raid/10
Should we adapt tests to click on 'yes' here?
Updated by riafarov over 6 years ago
Updated by riafarov over 6 years ago
Task is considered to be resolved, as initial adjustments were done and all smaller issues have to be aimed in separate tickets.
Latest PR for RAID: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3548
Updated by Anonymous over 6 years ago
- Related to action #23560: [sles][functional] test fails in partitioning_resize_root because needle partitioning-subvolumes-shown not found added
Updated by okurz over 6 years ago
- Status changed from Resolved to In Progress
Well, I'm sorry. I know we talked about this ticket today but it was really easy to find a job that shows what looks like basically only a small needle update would be missing to continue further: https://openqa.suse.de/tests/1168451#step/partitioning_raid/3 Or in other words, the already mentioned RAID scenario still does not work and is not blocked by bugs so we should continue here but of course you can search for another assignee.
Updated by riafarov over 6 years ago
- Assignee changed from riafarov to okurz
@okurz I thought we agreed during planning that we resolve this one, and create tickets for all other issues which come. So, I assign delegate this ticket to you, so you could keep track of it and we may create sub-tasks.
Updated by okurz over 6 years ago
- Target version changed from Milestone 10 to Milestone 11
blocked by subticket, moved to M11 as we have quite some tests failing in partitioning modules still
Updated by nicksinger over 6 years ago
I've noticed that the default behavior of a LVM-based system changed. Previously (SLE12SP3) an LVM-based layout did not include a separate home-partition in the default, resulting in just a single partition for "/".
Now (SLE15) a separate home partition is the default and therefore the test fails later on while checking the layout.
Either we adjust the needle in yast2_i which checks for the partition layout that it also includes the 2 extra partitions OR we change the text to not check the checkbox "Propose seperate home partition" earlier in the process of formatting.
Sorry if this is not the right bug to track this but IMHO this is definitely caused by the new storage-ng back-end yast2 uses now.
Updated by okurz over 6 years ago
- Subject changed from [sle][functional]Adaption to new yast storage stack to [sle][functional][epic]Adaption to new yast storage stack
Updated by okurz over 6 years ago
- Due date changed from 2017-10-11 to 2017-10-25
due to changes in a related task
Updated by okurz over 6 years ago
- Status changed from Feedback to Resolved
with the RAID adaptions done we can clos this now
Updated by SLindoMansilla over 6 years ago
- Due date changed from 2017-10-25 to 2018-01-16
due to changes in a related task
Updated by okurz over 6 years ago
- Due date changed from 2018-01-16 to 2018-01-30
due to changes in a related task
Updated by szarate over 3 years ago
- Tracker changed from action to coordination
Updated by szarate over 3 years ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html