action #39026
closedcoordination #17208: [sle][functional][yast][y][mandatory][medium][epic] LVM Thin Provisioning
[sle][functional][yast][y][mandatory][medium] LVM Thin Provisioning on SLE
0%
Description
Motivation¶
See motivation in parent epic
Acceptance criteria¶
- AC1: An openQA test scenario conducting installation on thin-LVM exists and is scheduled on SLE15
- AC2: Also on SLE12SP4 unless there is a clear message that thin-LVM is not supported on SLE12, see bsc#1027586
- AC3: Add support for other boot methods for the rest of supported architectures
Tasks¶
- Understand thin provisioning, e.g. watch https://youtu.be/E4H6Ar7XIjU or read https://www.theurbanpenguin.com/thin-provisioning-lvm2/
- Test thin-LVM installation manually on SLE15 and verify if bsc#1027586 is still there on SLE12SP4
- Resurrect https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2489 and adapt for storage-ng
- Get involved in https://bugzilla.suse.com/show_bug.cgi?id=1027586 to find out how tho handle the pre-storage-ng situation
- optionally keep it working for pre-storage-ng as necessary for SLE12SP4
- Add corresponding tests for all AC1 mentioned versions, distris
- Add support for PReP (ppc64), UEFI (arm), zipl (s390x)
Updated by riafarov over 5 years ago
- Copied from action #39023: [sle][functional][yast][y][mandatory][medium] LVM Thin Provisioning on openSUSE added
Updated by riafarov over 5 years ago
- Copied from deleted (action #39023: [sle][functional][yast][y][mandatory][medium] LVM Thin Provisioning on openSUSE)
Updated by okurz over 5 years ago
- Due date set to 2018-09-25
- Target version changed from Milestone 18 to Milestone 19
As discussed with riafarov, give some grace period after we have openSUSE tests now before we enable the same on SLE
Updated by mloviska over 5 years ago
- Status changed from Workable to In Progress
Updated by mloviska over 5 years ago
test works fine on sle15sp1, however sle12sp4 is still blocked by Can't create thinpool: LVM_LV_CREATE_FAILED: System error code was: -4014
Updated by mloviska over 5 years ago
Updated by mloviska over 5 years ago
- Status changed from In Progress to Feedback
PR is merged by now. I will enable the test for sle15sp1 since there has not been any issue observed yet. Regarding sle12sp4, I would rather enable it on dev group so we can label the failure with bug properly at least. Thus it should be easier to track it.
Updated by mloviska over 5 years ago
- Status changed from Feedback to Blocked
Updated by okurz over 5 years ago
I think this is nearly good enough. As stated in the parent ticket, a general acceptance criterion is always "test passes or fails in valid product bug" and I think we have that. https://trello.com/c/XghjsYUv/183-sle12-sp2-p2-1027586-cant-create-thinpool-lvmlvcreatefailed-system-error-code-was-4014 mentions that the priority of the issue might increase. I recommend to move the SLE12 scenario to the validation job group as well. Then we can close this progress ticket as "Resolved".
Updated by mloviska over 5 years ago
- Status changed from Blocked to Resolved
sle12sp4 dev group contains the job for all archs.
sle15sp1 dev group has the rest.